-
Notifications
You must be signed in to change notification settings - Fork 3
Description
(Just a note that things are working fine, and nothing is broken. But wondering if we should tweak the LAPL mapper.)
LAPL has updated their digital collections domain URL from tessa.lapl.org
to tessa2.lapl.org
.
Their OAI feed is giving us <dc:identifier>
withtessa2.lapl.org
URLs.
See example in: https://tessa2.lapl.org/oai/oai.php?verb=ListRecords&metadataPrefix=oai_dc&set=movie
with the first record having this identifier: <dc:identifier>http://tessa2.lapl.org/cdm/ref/collection/movie/id/0</dc:identifier>
However, it seems that when we harvest, we transform the tessa2.lapl.org
to tessa.lapl.org
to create our isShownAt
. When you click into a Calisphere item record, then click the link to point out to the LAPL record, you can see that the URL is tessa.lapl.org
then gets redirected to tessa2.lapl.org
.
See example in this record: https://calisphere.org/item/bfc418cd847f2e65a1dfa8c96ab58d53/
which includes a link to this record: https://tessa.lapl.org/cdm/ref/collection/movie/id/0
which redirects to this URL: https://tessa2.lapl.org/digital/collection/movie/id/0
Do we need to make any updates to the LAPL mapper?
https://github.com/ucldc/rikolti/blob/main/metadata_mapper/mappers/oai/content_dm/lapl_mapper.py