SFR-2452: CLACSO Mapping #501
Conversation
| [('isbn', '{0}|isbn')] | ||
| , | ||
| 'spatial': ('edition_location', '{0}'), | ||
| 'has_part': [('url', '1|{0}|clacso|application/pdf|{{"catalog": false, "download": true, "reader": false, "embed": false}}')] |
There was a problem hiding this comment.
Is there somewhere I can read about how these pipes work?
There was a problem hiding this comment.
Unfortunately no but you bring up a good point. Is there a way we can better abstract this data format or make it more readable?
There was a problem hiding this comment.
I agree that it should be a better way to showcase this data format and for right now the FRBRization process needs the data to be formatted in this way so this can be a future investigation in changing the format of the data the FRBRization process receives.
There was a problem hiding this comment.
Sounds good. Would y'all mind creating a ticket to investigate/refactor the has_part mapping logic/model when you get the chance? Thanks!
There was a problem hiding this comment.
@jackiequach to help cipher the has_part field, it's pipe delimited. The first part is the index of the part, the second part is the source, the third part is the media type, and the fourth part are the flags! The flags are the one that y'all see on the frontend to determine when to show the download and read online buttons or login!
There was a problem hiding this comment.
Thanks this is helpful!
There was a problem hiding this comment.
Sounds good. Would y'all mind creating a ticket to investigate/refactor the has_part mapping logic/model when you get the chance? Thanks!
I just made a ticket addressing this: https://newyorkpubliclibrary.atlassian.net/browse/SFR-2469
This PR focuses on creating a mapping for the new source CLACSO that will soon be added to the DRB ETL pipeline for ingestion.