Provide HTML content

[jimsafley]

The import process strips HTML from content before storing it as values. This is because markup can skew fulltext search results, and because Omeka escapes HTML anyway when rendering values. The principal reason for importing content should be to make the content searchable and available for text mining and analytics.

Even so, consumers need ways to access the marked up content. Two ideas of where to include the HTML content:

• on the item/media show page, in a separate "Scripto content" tab
• in the scripto_items and scripto_media API response.

[jimsafley]

Scripto now provides HTML content a) on the item/media show page, in a separate tabs labeled by the project's property, and b) in the item/media API response, under o-module-scripto:content.