Hello. I want to thank the OP for introducing this interesting use-case to the forum. I am a historian and have been using DT for my entire career now, and I have found it to be an excellent application for dealing with every type of media I use, including videos. Personally, time-referenced video data is not something I have used in the past or plan to use in the future, but it was nice to hear about how some users benefit from it.
-
feature requests
Speaking in general terms about how to deal with feature requests, not specifically about this one or the conversation so far, I think it’s a good idea to keep a few things in mind. (1) A feature request is a “request,” not a demand. (2) Any app developer has to balance each request against a number of factors–as users, we usually know the needs of a single person (ourselves) and what is an “essential” feature for one user may not: be of interest to others, be worth the time or money to implement, fit their roadmap, or be technically feasible. (3) What might seem simple to us is almost certainly more complex to implement–this is probably true of just about any request we make of anyone -
productive directions
In this case, I think speculating about the future growth of video as a resource for knowledge workers, the composition of the DT user base, or the number of people who would benefit from new video-related features isn’t a terribly productive direction for us to take the conversation. Even for the DT staff, it’s probably difficult to speak with any certainty about any of these factors. As Bluefrog mentioned, the user base is quite broad, and probably not something easily encapsulated in one sentence on a website, no matter how detailed the explanation. To be honest, I don’t even know if I am a “knowledge worker,” at least in the sense that Drucker meant it when he coined the term over half a century ago, unless you characterize my research and teaching as products and services. If Drucker were alive today, he might pigeonhole me that way, but I hope the knowledge I’ve created (am I a knowledge creator?) is a lot more than a mere commodity in a capitalist economy, just as we users are (I hope) something more than simply consumers of DT’s product. -
use cases
It might be more interesting (at least for me) to hear more about how someone is using the existing DT features to integrate video content into their databases, and through that discussion we might tease out some more concrete issues / solutions DT could consider for future improvements. It could also help other users discover new possibilities with the app. -
my example
By the way, I haven’t got any videos in my main DT database at the moment (I like that I “can” put them in any time, and I have had them in my database in the past). Even though I literally use videos on a daily basis in my teaching and research–I have a lot of videos on my computer’s hard drive and even more in my external drives–one reason I don’t have any videos in my database is that they take up a huge amount of space and this leads to problems with syncing. I tend to consider the bulk of my data (about four terabytes) as a kind of “library” or “repository” that I reference from my “curated” DT database of essential files for research projects (a text file might contain a mention of the file name of the video, for example). DT is one of several specialized applications I use to do things with my repository of data-. I could imagine using MarginNote to deal with some of the files I have, but the return on investment (time and money) would not be very appealing for me–my current “zettelkasten” database of text files connected by wikilinks seems to cover most of the stuff MarginNote would do for me. Still, I’ll experiment with it. -
my wishes and fishes
Ideally, I’d have all of my data in one place with one app (it’s really frustrating when I am looking for a file on my iPad during a business trip only to discover that it is on my external drive back in the office and totally inaccessible to me), and if I were going to hijack this thread and make a feature request, it would be to build an app that could manage four terabytes of data, but I am aware that there isn’t much out there for the average user that can deal with amounts of data that go beyond gigabytes (usually in the double digits at most), so even if DT was an enthusiastic supporter of my request, it is unlikely to get implemented anytime soon. I’d settle for just having my DT wikilinks that work so well in OSX available in iOS as well. If wishes were fishes, we’d all swim in riches!
Thanks again for the interesting discussion so far. Perhaps, like the wikilink example, there is something you can do, but a tweak here or there, an extension or adaptation of an existing design, might make it better. I look forward to reading more.