Advice needed - combining sophisticated keyword tagging w/ relational database (maybe InfoQube?)
< Next Topic | Back to topic list | Previous Topic >
Posted by Phil H
Jan 6, 2019 at 06:48 AM
I’d welcome advice on software that allows me to accomplish the follwing:
1. As I do research on particular topics (emerging technologies), I wish to enter bibliographic info (along w/ image and abstract) into a database of sorts for subsequent processing. Airtable and dedicated reference software can accomodate the standard stuff. The tricky part involves tagging each article with the appropriate keywords, easily and consistently.
2. Here is what I’m planning and where I’ve run into a brick wall.
a. Over the years I’ve tagged “free form” in Pinboard (using a #keyword convention). To tag more consistently I’ve constructed a taxonomy (really an ontology) with a controlled vocabulary containing (at present) 10 first-level categories, each w/ 4-20 2nd level, and some third-level terms, 300+ keywords in total. I’d like a solution that allows me to (i) show the taxonomy, initally collapsed; and (ii) allows me to open and select keywords from the appropriate sub-sections, rather than a lengthy, alphabetized list of all keywords. For example, for an article on GDPR, I would click to open Data, then click to open Privacy, and tag it the post by selecting the keyword “Regulation.” The most elegant approach I’ve found that accomodates “hierarchical keyword tagging” in iMatch (for digital images - see the Keywords Panel here https://www.photools.com/help/imatch/#visual_index.htm). Unfortunately, iMatch is for digital assets only, not web or pdf content.
b. To tag easily (quickly), I’d like to select from the controlled vocabulary (list of keywords), rather than having to type in the text. For any one post I may click on and assign 6-10 keywords, so the ability to select and assign keywords rapidly is essential.
c. Finally, to make the selected keywords available for more robust searching (e.g., using Boolean logic, as in #mobile #data #privacy #Europe), I’d like to export the list of keywords for a particular post along w/ the other bibiliographic info for that post (e.g., Title + author + source + abstract + #keyword1 #keyword2 ... #keywordn).
So, in essence I’m looking for a solution that combines elements of a relational database (for the standard bibiliographic info) with the sophisicated and efficient keyword tagging capability of iMatch. I’ve learned about InfoQube on this forum and it looks promising - would welcome (i) feedback on the approach above, and (ii) recommendations on how best to accomplish (1) and (2).
Thanks!
Phil H
Posted by Alexander Deliyannis
Jan 6, 2019 at 09:39 PM
I let Pierre answer on InfoQube’s tagging approach and overall suitability for what you want to do, but in respect to the hierarchical organisation, I’ve found the implementation in (the now no longer developed) Surfulater ideal and, sure enough, Neville Franks has followed the same logic in his newer offering, Clibu: https://clibu.com/
Phil H wrote:
>The most
>elegant approach I’ve found that accomodates “hierarchical keyword
>tagging” in iMatch (for digital images - see the Keywords Panel here
>https://www.photools.com/help/imatch/#visual_index.htm). Unfortunately,
>iMatch is for digital assets only, not web or pdf content.
Posted by Phil H
Jan 7, 2019 at 06:36 AM
Thank you, Alexander - Clibu does indeed offer a collapsible Tags Tree panel. According to their website:
*** “Tags can be nested, allowing true hierarchical content organization.” ***
I will take a closer look!
Phil
Alexander Deliyannis wrote:
I let Pierre answer on InfoQube’s tagging approach and overall
>suitability for what you want to do, but in respect to the hierarchical
>organisation, I’ve found the implementation in (the now no A collapsible Tags Tree panel to create, select, rename and move Tags. Clibu’s Tags can be nested, allowing true hierarchical content organization.
>developed) Surfulater ideal and, sure enough, Neville Franks has
>followed the same logic in his newer offering, Clibu: https://clibu.com/
>
>
>
>Phil H wrote:
>>The most
>>elegant approach I’ve found that accomodates “hierarchical keyword
>>tagging” in iMatch (for digital images - see the Keywords Panel here
>>https://www.photools.com/help/imatch/#visual_index.htm).
>Unfortunately,
>>iMatch is for digital assets only, not web or pdf content.
Posted by Phil H
Jan 7, 2019 at 07:09 AM
Took a closer look at Clibu - offers a collapsible Tags Tree for searching for tagged articles, but not for assigning tags (e.g. list for assigning tags is simply a list of all available tags - organized by parent, but categories of tags aren’t collapsible). With a 3-level taxonomy and 200+ tags I need a collapsible UI. Not sure why the developer has implemented collapsible tag list for finding but not for assigning. Will look at alternatives.
Phil
Phil H wrote:
Thank you, Alexander - Clibu does indeed offer a collapsible Tags Tree
>panel. According to their website:
>
>*** “Tags can be nested, allowing true hierarchical content
>organization.” ***
>
>I will take a closer look!
>
>Phil
>
>Alexander Deliyannis wrote:
>I let Pierre answer on InfoQube’s tagging approach and overall
>>suitability for what you want to do, but in respect to the hierarchical
>>organisation, I’ve found the implementation in (the now no A
>collapsible Tags Tree panel to create, select, rename and move Tags.
>Clibu’s Tags can be nested, allowing true hierarchical content
>organization.
>>developed) Surfulater ideal and, sure enough, Neville Franks has
>>followed the same logic in his newer offering, Clibu:
>https://clibu.com/
>>
>>
>>
>>Phil H wrote:
>>>The most
>>>elegant approach I’ve found that accomodates “hierarchical keyword
>>>tagging” in iMatch (for digital images - see the Keywords Panel here
>>>https://www.photools.com/help/imatch/#visual_index.htm).
>>Unfortunately,
>>>iMatch is for digital assets only, not web or pdf content.
Posted by Pierre Paul Landry
Jan 7, 2019 at 03:33 PM
Alexander Deliyannis wrote:
I let Pierre answer on InfoQube’s tagging
I’m on holidays this week, but this user manual page explains tags quite well
https://infoqubeim.com/drupal5/?q=node/4328
The main improvements over other tags implementations is the multi parent hierarchical features
Pierre