8564_ for Books and Proceedings

[agentilb]

In this field, we find 3 types of information:

1. URLs to the ebooks or e-proceedings, this should be stored at the holding level (when $$y contains "ebook" or "e-proceedings", $$u .-> holding.yml/url.yml/value, $$y -> holding.yml/url.yml/description)
2. External URLs (Conference homepage, Website...), there is an entity for this in the Data Model. ($$u -> url.yml/value and $$y url.yml/description)
3. Links to CDS files, if a file is attached to the record.

Question: regarding this 3rd case, for the time being, there is no rule for the subfields 8564_ $$x, $$8 and $$s for the time being, because I did not know how you want to handle this in the new system. Should this information be migrated? And where?

( requires #200 )

[kpsherva]

the ticket concerns making a decision about how should we migrate subfields _x, _8, _s as they probably contain legacy specific information <- to check, example record: https://cds.cern.ch/record/2312429/export/hm?ln=en

[equadon]

As discussed _x is legacy connected information to be decided what to do.