Allow customization of which OCLC subfields populate requests
OCLC has recently rolled out URIs in their various author/creator fields (100/700/etc.), which is causing many author names to be pulled into ILLiad with long website addresses that clutter our paperwork. It would be helpful if we could choose which subfields from OCLC records we wanted to import, so that we could suppress subfield 1 in the author field. Ideally, this would work both for the "Copy Info" button and for the mechanism that populates the OCLC request form, so that we could automatically avoid sending the URIs out to our lending partners as well.
Jenny Vitti
shared this idea
-
Jesse Thomas
commented
I'm so glad to see that someone else submitted this enhancement request!! We met with Atlas earlier this morning to talk about some of the other subfields that have been cluttering up our requests. The 100 field is the most glaring. We don't need ‡1 (Real World Object URI), and we also want to hide ‡d (Dates associated with a name), ‡e (Relator term), and ‡6 (Linkage). Our library owns lots of Mongolian and Chinese books. This is what our Author data looks like in those cases.
880-01 Masuho, Zankō, 1655-1742, author. https://id.oclc.org/worldcat/entity/E39PBJfmvjWGkcDTQk7FCB
All we really want is ‡a. Having the ability to customize which subfields get populated would be a huge improvement!
-
Jacob Fontenot
commented
Suppressing subfield 1 may be the most elegant fix. If not possible, might you be able to parse the author/creator fields, detect urls, and not import them at all?
-
Anonymous
commented
Please remove the clutter.
-
Anonymous
commented
Agree!