Support for non-literal data types (Resource/URI) in Omeka S Export

[lucchesia]

Currently, the Tropy Omeka S plugin exports all metadata values as literal strings. Users who utilize Omeka S as a relational database need the ability to export values as Resource Links (pointing to other items/resources within Omeka) or URIs.

Without this, users must manually re-type or bulk-edit every field in Omeka S to convert "text" into "links," which breaks their Tropy-first workflow.

We need a way to "flag" or "type" a metadata field so the Omeka S plugin knows to send it with the correct @type via API.

Perhaps a data type toggle in the template Editor (e.g., String, URI, Resource ID)?

prompted by a discussion on the Omeka Forum where the user is struggling to maintain relational data when moving from Tropy to Omeka S (https://forum.omeka.org/t/tropy-omeka-s-with-field-of-omeka-s-item-data-types/28516)

[inukshuk]

Yes, we can use data type 'URI' in the Tropy template for this purpose. The plugin can use this information to upload those values as links.

[lucchesia]

thanks a lot!