yalelibrary / YUL-DC

Preliminary issue tracking for Yale University Libraries Digital Collections project
3 stars 0 forks source link

ASpace Mappings should use translations for "linear feet" and "mixed materials" #1029

Closed dl-maura closed 3 years ago

dl-maura commented 3 years ago

Story

For example, right now Linear Feet is coming through as linear_feet, Mixed Materials is coming through mixed_materials.

Acceptance

FCRodriguez7 commented 3 years ago

Both linear feet and mixed materials have underscores.

Linear Feet image.png

Mixed Materials image.png

mikeapp commented 3 years ago

So this is still an issue, we'll need to consult with YAMS. For "linear_feet" see https://collections.library.yale.edu/catalog/31960579

DraxIndustries79 commented 3 years ago

Check after 7/21 MC update. We may get a fix on this.

FCRodriguez7 commented 3 years ago

waiting for the last ingest process to complete.

FCRodriguez7 commented 3 years ago

List for mixed_materials 10001148 2052809 2052784 17145211 17167797

MaggieZhaoYale commented 3 years ago

Frederick and I paired to find linear feet in some of the records. We found that the object no more has extent as a result in the metadata cloud. The last update to the ASpace record was July 20th. We need to investigate this issue.

mikeapp commented 3 years ago

@martinlovell Perhaps missing values are related to MC issue #277 - looking only in the leaf nodes for extent values? Is the next ticket for MC investigation or should we ask Mark/DSU for an example?

MaggieZhaoYale commented 3 years ago

@mikeapp Mark confirmed that extent is only in the leaf nodes last week. I will ask Mark for an example.

MaggieZhaoYale commented 3 years ago

https://collections-test.library.yale.edu/management/parent_objects/10719304 has the extent "16 pages" https://collections-test.library.yale.edu/catalog/10719304,

MaggieZhaoYale commented 3 years ago

Mark added "16 pages" as the first extent, and a second extent subrecord (1 linear_feet, which should show up as 1 linear feet), but it's not showing up, even after updating the object. Metadata cloud does not show the second extent https://metadata-api-test.library.yale.edu/metadatacloud/api/1.0.1/aspace/repositories/11/archival_objects/204680?mediaType=json.

Updated: Martin restarted MC on test, and the changes are showing up. https://collections-test.library.yale.edu/catalog/10719304 (1 Linear Feet in extent)