search

UCSCLibrary / NuxeoLink

This Omeka plugin adds the ability to navigate a Nuxeo DAMS and import Nuxeo documents as Omeka items. Designed specifically for use with the UCLDC Nuxeo DAMS.
5 stars 0 forks source link

Metadata mapping #2

Closed JessWaggs closed 9 years ago

JessWaggs commented 9 years ago

Need to map core/basic elements to Omeka DC schema according to metadata map (https://docs.google.com/a/ucsc.edu/spreadsheets/d/1UYml7kcOgipWZxgx27-sqUXUUThMwRf55lV8gv8f1vY/edit?usp=sharing)

Remaining metadata can go into special UCLDC schema.

Or, if possible, give user the choice between the two when configuring?

NedHenry commented 9 years ago

These elements should now be mapped to Dublin Core as specified in the newest version of the plugin. I have tested this with one or two Nuxeo objects, but some further testing with different UCLDC objects would be a good idea.

JessWaggs commented 9 years ago

Back to the future : ) The above doc has been revised to reflect two options: Option #1: everything goes into the DC field specified in the UCLDC Metadata Model Option #2: everything goes into the reproduced UCLDC Scheme and nothing into Omeka DC

NedHenry commented 9 years ago

This should be working in the new version of the plugin, but it could use some further testing to make sure it works for all items.

JessWaggs commented 9 years ago

Initial testing:

JessWaggs commented 9 years ago

Tested four additional imports. The following metadata are not being passed from UCLDC into the Omeka UCLDC scheme:

NedHenry commented 9 years ago

Thanks for the tests! I'm working on these issues, but here are some quick thoughts.

  1. The "language" being pulled as "Array" is an easily fixable mistake, which I already corrected on my own machine. The next update will deal with these properly.
  2. Both Omeka and Nuxeo like the "Title" to be stored in Dublin Core to display properly. Nuxeo actually passes me the item titles as part of the dublin core, which otherwise just stores administrative metadata for them. I will find a way to copy it over to the UCLDC schema as well, if it is installed. I think that all Omeka items should have their titles in the Dublin Core Title field for proper display in Omeka, even if the title is duplicated in the UCLDC schema title field.
  3. I am not sure about the elements you listed which aren't being mapped into Omeka. I will have to look into those. It is possible that the Nuxeo API is not sending all of the item metadata along, but I will find out.

Best, Ned

On Mon, Dec 15, 2014 at 2:28 PM, Jess Waggoner notifications@github.com wrote:

Initial testing:

  • looks like "Title" is still being pulled into Omeka DC even though plugin is configured to use UCLDC
  • language is being pulled in as "Array" for all objects

— Reply to this email directly or view it on GitHub https://github.com/UCSCLibrary/NuxeoLink/issues/2#issuecomment-67078403.

JessWaggs commented 9 years ago

I thought something like that might be the case with the Title. If it is in both DC and UCLDC Scheme won't it appear twice in the item record?

NedHenry commented 9 years ago

The title will display twice if the theme is configured to display all metadata. This is the default for some themes, but is probably not what people will do in any production site. Still, you know better than I do what people would find useful. We could put the title in either schema, or both. Best, Ned

On Mon, Dec 15, 2014 at 3:44 PM, Jess Waggoner notifications@github.com wrote:

I thought something like that might be the case with the Title. If it is in both DC and UCLDC Scheme won't it appear twice in the item record?

— Reply to this email directly or view it on GitHub https://github.com/UCSCLibrary/NuxeoLink/issues/2#issuecomment-67088266.

JessWaggs commented 9 years ago

Let's put the title in both and we can add this to the documentation. We can also test the use of the "Hide Elements" plugin for hiding the UCLDC scheme title. Could be a good option for folks who don't want to or can't customize their theme.

NedHenry commented 9 years ago

I issued an update which fixes these issues. It seems to work well on the exhibits.dev site, but I have not tested it very thoroughly (only with one or two objects). The problems were from bugs in the upgrade process; the UCLDC schema elements in the omeka database did not upgrade when the plugin upgraded, so the plugin was mapping the new fields to nonexistent elements. I think the mapping is working properly now, including the duplicated titles. Please re-open this issue if you find otherwise. Thanks for the quick testing, and sorry for the buggy upgrade!

JessWaggs commented 9 years ago

It looks like we are now missing the following fields (I'm using the UCLDC field labels):