You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Yes. Managing many, many CT documents in a desktop. There are provisions for bookmarking nodes within a CT document. But there is nothing to bookmark or cross reference elusive documents tucked away in the desktop. Describe the solution you'd like
Create a desktop CT node cataloguing system. This is a bigger task than might be realised. But in effect a vector database connecting nodes across multiple CT documents. One tool which is an invaluable help is Recoll where queries such as [ext:ctd "search terms"] can be used to find documents with extension ctd containing search terms.But this assumes that you remember terms to search. A fuller solution would be a desktop wide corpus ("hopper") of words found in all ctd documents, using corpus linguistics tools. Rather than coding this as a new feature in next generation CT perhaps a paper explaining how to setup such a toolchain.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Yes. Managing many, many CT documents in a desktop. There are provisions for bookmarking nodes within a CT document. But there is nothing to bookmark or cross reference elusive documents tucked away in the desktop.
Describe the solution you'd like
Create a desktop CT node cataloguing system. This is a bigger task than might be realised. But in effect a vector database connecting nodes across multiple CT documents. One tool which is an invaluable help is Recoll where queries such as [ext:ctd "search terms"] can be used to find documents with extension ctd containing search terms.But this assumes that you remember terms to search. A fuller solution would be a desktop wide corpus ("hopper") of words found in all ctd documents, using corpus linguistics tools. Rather than coding this as a new feature in next generation CT perhaps a paper explaining how to setup such a toolchain.
The text was updated successfully, but these errors were encountered: