Closed jacobthill closed 4 months ago
It looks like the URL you pasted above is requesting the oai_dpla
metadata format?
I guess it is picking up the wrong metadata_prefix
somehow. It should be oai_dc
right?
For whatever reason it doesn't look like their oai_dc
metadata flavor contains dc:description
elements?
If you want to harvest the oai_dpla
flavored records I think we will need to update the oai_xml driver so that it's aware of that namespace?
https://github.com/sul-dlss/dlme-airflow/blob/main/dlme_airflow/drivers/oai_xml.py#L14-L18
Good catch Ed, I tried both but didn't notice the description was only in the oai_dpla version. I will see if I can add that namespace
i got it working, thanks Ed
Looking at the ucla armenian_manuscripts collection view-source:https://digital.library.ucla.edu/catalog/oai?verb=ListRecords&metadataPrefix=oai_dpla&set=member_of_collection_ids_ssim:d2xg9000zz-89112
The records have values for
dc:description
anddc:identifier
but neither of these show up in the harvested data. There is anidentifier
field in the harvested data but it contains values fromedm:object
andedm:isShownAt
. The other values with a dc namespace are harvested without specifying a path and the other values with an edm namespace aren't harvested at all as far as I can tell. I've tried configuring the paths for these fields but can't get it to work.A typical OAI record looks something like this:
The ucla records have an additional element under
metadata
and above the data fields:This might be causing the unexpected behavior.