Introduction and question on roadmap

My first posting here. I have a couple of initial observations and a general question about the strategic direction of this interesting product.

My normal day job is running an information management consultancy specialising in building semantic web based information architectures; commonly called knowledge graphs. I have been intrigued for many years by the problem of information discovery in web systems, but increasingly also in local file system management. Ironically, since I spend my day advising enterprises on how to build structured networks of linked information, I’m pretty hopeless when it comes to managing my own information. I suffer from all of the usual information problems - I can’t remember where I put something, I know that a document belongs to more than one context but can only choose one, I want to specify more than just a general link from stuff to other stuff, by showing how they are linked. And so on.
I came across Hook recently and thought it might help me with some of these information problems, by providing a means of linking one content object to another or to a project, or a person, or something else. It certainly has the indications of the kind of thing that I want to use.

So that brings me to my question on where the product is going. I’d really like to be able to link the document I’m writing, or the image I’m creating, or whatever, to another information object representing the project or the client, with some sort of semantic link such as “this document has project X1234”. Such a link should, as it would in an ontology-based model, have an implicit inverse relation such as “these pieces of content are linked to this project”. It feels to me as though Hook might be the type of product that could develop in this direction, if it were possible to frame it around a semantic information model with classes representing the kind of content object or other thing that needs to be linked. This kind of thing is actually pretty straightforward for web-based information systems, but of course they don’t deal with files in a file system, rather content objects in an information system. So I understand the challenge!

It would be interesting to know whether any of these ideas have any resonance with your plans for Hook.

1 Like

Welcome to the Hook Productivity Forum, @tellurasemantics. And what an excellent post, question!

just a short reply (from a resort) for now.

There’ve been quite a few suggestions / requests on this forum. We’ve responded to several of them, and disclosed near term product road map. No one here to my knowledge had explicitly requested labeled links — but I believe it came up during the private beta prior {to the public beta that started in Jan 2019}.

Near term includes supporting multiple macs (private beta about to start – long delayed) and recent items.

In the new year, I intend to write a post about some of the future of Hook that deals with aggregation, which are related to requests that have come up on the forum (search for “tag” and “project” to see some of that). I’ll be interested to hear whether you feel that sufficiently addresses the underlying requirements to which you are alluding. It’s not explicitly labeled links, but something logically similar.