You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realize the technical difficulty is that we don't look at sites and their URLs when importing items directly from the installation. But this does seem less than ideal.
Is there a way to improve this? Can the API identify which sites an item is part of, and then the importer can translate that to the first URL in the list? I know from the python export script that we provide an item's sites by ID ("1|2|4" etc.) but do we send the slug somewhere?
The text was updated successfully, but these errors were encountered:
Rather than a direct link to an Omeka item in a site, the OSII
osii:source_resource
link is to the API, i.e.https://explore.saltairecollection.org/api/items/13698
rather than
https://explore.saltairecollection.org/s/p/item/13698
on
http://dev.omeka.org/amayer/amayer-s/omeka-s/s/my-omeka-s-site/item/21713
I realize the technical difficulty is that we don't look at sites and their URLs when importing items directly from the installation. But this does seem less than ideal.
Is there a way to improve this? Can the API identify which sites an item is part of, and then the importer can translate that to the first URL in the list? I know from the python export script that we provide an item's sites by ID ("1|2|4" etc.) but do we send the slug somewhere?
The text was updated successfully, but these errors were encountered: