-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[OBSOLETE] fields, subfields, character positions #339
Comments
@junghaelee identified the following problems with the 00x spreadsheet:
@mcm104 will follow up on these (thank you!) @SitaKB is this what you were asking about/related to the problems you were asking about in #50 ? |
@CECSpecialistI Yes, these are the issues I encounter in the 00x spreadsheet. |
Thanks @SitaKB ! |
OCLC's Response: Thank you for contacting OCLC Customer Support. I checked with my colleague regarding your question. We cannot provide a list of obsolete fields/values which still have data in bib records. However you could get this information by running a normal "li:" query using a query collection and then using MARC edit to pull out each field that is obsolete to see what data is entered there: Please let me know if you have any additional questions, Best, |
We will need to check on whether obsolete fields/subfields/character positions are being used in source data ourselves. Since they are obsolete, we will not prioritize this work right now, and will put off mapping obsolete fields/subfields/character positions until at least the end of the PCC RDA BSR/CSR milestones. Decision |
We decided on 2022-04-13 that we should map obsolete fields/subfields/character positions if they are present in OCLC database. To find out which are used and which are not, Junghae will assemble a list from everything marked [obsolete] in the spreadsheets, and send to OCLC for review. Busy this week, likely sometime next week. Thank you @junghaelee for tackling this one!!
The text was updated successfully, but these errors were encountered: