Bug 838537 - Content Enrichment
Summary: Content Enrichment
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Topic Tool
Classification: Other
Component: FUDCon Docs Hack
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Joshua Wulf
QA Contact: Joshua Wulf
URL:
Whiteboard:
Depends On: 839111
Blocks: 699089
TreeView+ depends on / blocked
 
Reported: 2012-07-09 12:09 UTC by Joshua Wulf
Modified: 2014-10-19 23:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-07 14:55:23 UTC
Embargoed:


Attachments (Terms of Use)

Description Joshua Wulf 2012-07-09 12:09:27 UTC
Add Content enrichment (concept link suggestion) to the editor:

Take the POC at http://www.atmayogi.com/node/5095 and implement.

Canonical instances of topics need to be published to docs.redhat.com

1. Investigate publishing a "book" that does not appear in the TOC. Remove all next and previous links from the brand used to publish the book. 

2. Make the URLs deterministic. The TopicID is unique in the namespace; base it on that so that the SKOS vocabulary can be generated programatically.

3. Write a publishing script to scan a book that is "published" to extract the topics; compare them with the "published list"; generate SKOS metadata for them and add a canonical instance when they are not already published.

4. Update the enrichment endpoint index with the published data periodically.

5. Style the enriched links so that they are low noise. Perhaps remove the underline from those links.

6. Persist triples describing the published canonical instances to a triple store. This is the "published list". When / if the canonical instances are ever moved it can be used to create owl:sameas triples to point to the new instances, and Apache redirect files can be generated programatically.

Comment 1 Joshua Wulf 2013-04-22 09:03:36 UTC
This is a good candidate for a feature for the Death Star editor.


Note You need to log in before you can comment on or make changes to this bug.