I am using the Tropy “Omeka S” plugin to export to my Omeka S installation. Works well. It imports into an Omeka S resource template that includes a field with the data type (from a custom vocabulary) of an Omeka S item. Is there anyway to get it to connect the imported field to an Omeka S item?
I know this can be done via the CSV import module, but that doesn’t include the media.
I’m looking for a workflow where I can assign the value of all fields in Tropy (including the value of the field with the data type of Omeka S item), so I can do all my work in Tropy and simply export to Omeka S.
What does it come in as currently? Just text? What are you filling in there on the Tropy side?
My guess is that this will be challenging for Tropy to support as this data type comes from a module and is going to be a little more site-specific, where their exporting code is necessarily going to be more generic and doing things that will work on any site.
Thanks! It’s exported as text right now, and it appears that Omeka adds a field to my template to accommodate the import. Does anyone know if there is a data type for an Omeka Item? Maybe I could export it as that data type, and maybe Omeka would import it?
Hi @dernst (not sure we are talking about the same thing here, but to add my 2 cents)
What I normally do is creating Resources Templates on the Omeka S that fully map and mirrors the properties of all the fields I have on my Tropy custom metadata templates. Once this is done, from your Tropy plugin configuration tab, you can simply add one or more instances of the Omeka S plugin adding the ID of your Resource Template in the last settings field “Resource Template ID”.
Steps to find the Resource Template ID from your Omeka S admin dashboard:
In the left-hand navigation menu, go to Resources > Resource Templates
On the Resource Templates page, you will see a list of all available templates. Click the edit icon (a pencil) for the specific template you want to use
Once the edit page for that template loads, look at the URL in your browser’s address bar
The ID-NUMBER is a numeric value found at the end of the URL
e.g., for <your-omeka-s-url/admin/resource-template/14>, the Resource Template ID is “14”
If you need any further assistance on the Tropy side of things, drop us a line on the Tropy forums.
Thanks! Yes, I’ve done all of that, and it works quite well. The sticking point is that one of the fields in my Omeka S Resource Template is an Omeka S Item (as part of an item set). Here are the specifics:
I have two item sets: (1) Media and (2) People.
I am importing photographs into the Media Item Set from Tropy via a Resource Template. One of the fields in the Omeka S Resource Template comes from a Custom Vocabulary, which defines the field as an Item from the People Item Set.
I’d like to identify the people in the photo in Tropy so that they import into Omeka S as pointers to People Items I have in Omeka S. I know I can go into Omeka after the import and connect them to the People Items, but I’m trying to do all of the data entry in Tropy.
Thanks , I see what’s happening now. To fix this, we’d need a more site-aware export logic in Tropy. Essentially, Tropy needs to know that some fields aren’t just text notes (strings), but ‘Resource ID’ that Omeka should treat as a link.
I’m taking this back to the Tropy team to discuss. Since these data types can be quite site-specific, we’ll need to think carefully about how to support them without losing the generic flexibility Tropy needs. I believe there might be a way to do so if metadata fields are not flatten on the Tropy side. We have to find a way to ‘flag’ certain fields in your templates so the plugin knows to send them as resource links rather than just text. I hope we can find a way to improve this!
In the meantime, I hope you can ease your workflow with the ‘Bulk Edit’ feature within Omeka S after your export.
@dernst One other question that will inform what’s possible: what are you putting in the Tropy field for this now? The Omeka S internal item ID? A URL? Something else?
I’m just putting in the name of the person for now, although I know that’s not going to get me anywhere. I’d be happy to put in the ID if there was a way to convert it to an Item once in Omeka.