I might be completely off base here, and I’m sorry if it’s dumb.
I was reading about the academia problem, and in implementing JD myself (I am no scholar, just a retail manager) I’ve noticed something. What if, instead of treating IDs as endpoints, as destinations, we tread them as tags for a multitude of things in a wide range of applications?
Your index becomes exactly that. An index of everything, across all the systems you have. But sometimes, in the index, at 14.04, you have a little note that tells you [In use as tag in Zotero, Akiflow]
When you go to Akiflow, your task manager of choice, 14.04 is a tag for all tasks relating to 14.04.
You go to Zotero, and 14.04 is a tag for all the research pertaining to 14.04.
14.04 might be a project!..it also might be a subject you’re currently tracking.
It would allow breathing room when the index is restrictive, and become the One Index to Rule Them All.
Why I’m thinking about this is that in our lives, we have many many apps, many services, and our data doesn’t live in one place. Additionally, the more time passes, the less we are dealing with files, and the more we are dealing with data.
JD as a universal tag system could be the answer to taming the wide ranging data web our lives our composed of. A way to tame all the discrete data units that come into our lives on the daily.
It would make changes like for examples, tasks wouldn’t go into the index. It would use the index. If it makes sense.
As long as the index is filled properly with [where data is now], it should allow you to tame everything, to organize properly, and the index would still be exactly that. An index for your life.
What do you think? Am I insane?