Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow CTM topic map sources should be able to have their full-text indexes maintained just like XTM and LTM topic maps #390

Closed
GoogleCodeExporter opened this issue Mar 16, 2015 · 4 comments
Closed

Allow CTM topic map sources should be able to have their full-text indexes maintained just like XTM and LTM topic maps #390

GoogleCodeExporter opened this issue Mar 16, 2015 · 4 comments
Labels
Component-Engine Enhancement GoogleCode Newbie Priority-Low Release5.2.0

Comments

@GoogleCodeExporter
Copy link 

The tm-sources.xml configuration file currently allows one to specify 
maintainFulltextIndexes value="true" for XTMPathTopicMapSource, 
LTMPathTopicMapSource and TMXMLPathTopicMapSource files but not for 
CTMPathTopicMapSource files. It is cumbersome to have to maintain the full text 
indexes for CTM files manually while other topic map sources are taken care of 
automatically. It would be nice if Ontopia would support this.

Original issue reported on code.google.com by dan.sp...@gmail.com on 4 May 2011 at 3:36
@GoogleCodeExporter
Copy link
Author 

Yes, they should. This can basically be done by making the 
CTMPathTopicMapSource subclass AbstractOntopolyTopicMapSource. A patch to do 
this would be very much welcome, and shouldn't be too hard to produce.

Original comment by lar...@gmail.com on 5 May 2011 at 7:00

  • Changed state: Accepted
  • Added labels: Component-Engine, Newbie

@GoogleCodeExporter
Copy link
Author 

So let it be written, so let it be done :-)

The attached patch implements what Lars M has suggested. The one thing that I 
am not quite up to doing is making a CTMWriter (which the 
AbstractOntopolyTopicMapSource class wants) so I punted on that. I have tested 
this by loading a CTM file in Omnigator, creating a full-text index, modifying 
the underlying .ctm file and "reloading" to topic map from Omnigator and a new 
FT index is created.

Original comment by dan.sp...@gmail.com on 15 May 2011 at 7:12

Attachments:

@GoogleCodeExporter
Copy link
Author

Original comment by lar...@gmail.com on 18 Aug 2011 at 6:52

  • Added labels: Release5.2.0

@GoogleCodeExporter
Copy link
Author 

Thank you for the patch! Applied now in revision 2169.

Original comment by lar...@gmail.com on 18 Aug 2011 at 8:03

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component-Engine Enhancement GoogleCode Newbie Priority-Low Release5.2.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter