search

uhlibraries-digital / bcdams-map

Metadata Application Profile for the Bayou City DAMS
MIT License
6 stars 5 forks source link

Add Crosswalk Attribute #66

Closed metaweidner closed 7 years ago

metaweidner commented 7 years ago

This will facilitate mapping to other metadata schema such as MODS for Avalon.

seanlw commented 7 years ago

Avalon MODS crosswalk https://github.com/uhlibraries-digital/bcdams-map/wiki/06-Avalon-Crosswalk

metaweidner commented 7 years ago

abe616ef9545949a9000bd98aa49e6235019e166 ecdf0195810b581d060be605228c08ab776f5b06 65858874702646674e3e4383133f309afc624ffb

seanlw commented 7 years ago

@amgaynor Since the addition of note types, can you map out the MAP fields with the appropriate Note Types.

https://github.com/uhlibraries-digital/bcdams-map/wiki/06-Avalon-Crosswalk

@metaweidner once this is done there will be more changes in the crosswalk attribute, I'll let you know what that might look like depending on what gets mapped.

amgaynor commented 7 years ago

@seanlw I've updated it with the notes that we had worked on before. Though I'm still interested to hear @metaweidner and others' thoughts our (ab)use of the Note field, bearing in mind that it's a bit of a stopgap measure.

seanlw commented 7 years ago

@metaweidner can you add in the crosswalk segments to Collection, Preservation Location, and Donor. Because these share the same field Note, add the attribute type to the avalon attribute. The type is defined in the crosswalk wiki page. Also, please add type general to uhlib.note field.

example:

crosswalk:
  avalon:
    label: note
    type: collection
metaweidner commented 7 years ago

@seanlw Will these mappings work for now, assuming that we can get the Identifier ingest to work? It seems like Collection is already captured in Avalon's Collection and Unit facets.

Donor

crosswalk:
    avalon:
        label: note
        type: donor

Preservation Location

crosswalk:
    avalon:
        label: identifier
        type: preservation location

Identifier

crosswalk:
    avalon:
        label: identifier
        type: other
seanlw commented 7 years ago

@metaweidner yeah, I think that will work

metaweidner commented 7 years ago

@seanlw I added Collection to the mix as well given the limitations of the MAP in identifying the Collection and Unit for Avalon ingest. https://github.com/uhlibraries-digital/bcdams-map/commit/de6b429e8b535cfdcfa176e5f88a65505377aab6

seanlw commented 7 years ago

@metaweidner I noticed that the avalon label for Other Identifier has been changed to identifier. It will need to remain Other Identifier. I know the Identifier Type is giving us trouble but I do know it will fail if Other Identifier is not there.

metaweidner commented 7 years ago

@seanlw 7dd0541a3e47054bab050ff57f2d39358cc55e29

seanlw commented 7 years ago

@metaweidner some changes are needed to the avalon crosswalk

metaweidner commented 7 years ago

@seanlw aa3a77e

amgaynor commented 7 years ago

@metaweidner @seanlw I've updated the Avalon Crosswalk wiki page to include the ASpace URI mapping.

We'll need the avalon crosswalk added to the MAP for the Brays export.

I think:

ASpace URI

crosswalk:
    avalon:
        label: "other identifier"
        type: "aspace uri"
metaweidner commented 7 years ago

@amgaynor @seanlw added aspace uri avalon crosswalk aef1409

seanlw commented 7 years ago

I've pushed this change to production so you have access to it now