TechCall_29feb2016

Agenda

• ISSNs and legacy serials - tabled for next call that Martin can join
• Recap of EABL workshop, including upcoming requirements for Macaw, Admin Dash, and portal - tabled for next call that Martin can join
• Treating Contributor and Licensor as controlled vocabularies in BHL (tabled for when Joel and Mike are both available)

Review of previous action items
• Susan will email Keri to better understand how Z39.50 is working at SI.
• Susan will talk to Bianca about the Cataloging Working Group and preferred use of author names vs name at time of publication.

Notes
Martin, Mike, Trish, Susan L, Carolyn

ISSNs
Background Discovery Tools Working Group was looking at OCLC ISSN data requirements for ingesting records, and legacy materials would not necessarily have those. Additionally, even the legacy physical item had an ISSN, it sounds like the digital surrogate also needs an ISSN. JSTOR rep visited NYBG and supposedly digital copies require e-ISSN.

Benefits of adding ISSNs Improved compliance with data requirements for discovery systems. Would also simplify things for getting a DOI from CrossRef

Risks If we don’t do this, does that mean those serials without ISSNs can’t be added to Summon? to DPLA? Haven’t heard that would necessarily be the case.
It will complicate assigning DOIs to the legacy serials Normal way to register for DOIs won’t work without the ISSN. We would have to set it to a particular genre which may not be entirely accurate or at least could be potentially confusing. In other words, it would require a kludgy way of doing it and could mess up discovery because of how CrossRef accepts and processes.

Potential Costs Mike did some research on costs and found: resolution services start at 1158 euros (was unclear if would be one time or annual);
Or download data for 8160 euros and we’d still need to store the data and build our own search/resolution tool on top of it;
Or Data file of entire ISSN register for 19,678, still requiring us to build search/ resolution tool ourselves

Priority? MRK: Not in realm of feasibility over the next year. We can revisit in 2017.

EABL: Follow-up on tech-related action items identified at EABL Workshop
1. Susan and Trish submitting a Metro proposal for deduplication tools. Trish is drafting and Susan will submit, hopefully later this week. Metro hosts the fellows.
2. Harmonizing terms throughout BHL, changing Contributing Library to Contributors: Mike changed throughout BHL. Joel will change in Macaw. Susan Lynch had a phone call with Bianca, she’s already changing all of the documentation for that.
3. Articles: When would we ever provide RIS files to Rod as part of our regular workflow? Mike suggested this as more of a one-off to respond to the ongoing demand to provide article level metadata through Macaw. This was meant as a stop gap while a more ideal workflow is established. We can also supply CSV files in place of RIS. No actions for articles at this point. If EABL team identifies something requiring tech development, Susan will bring it to the group for discussion.

NOTE For technical development changes, article or otherwise, Martin will approve those as priorities as part of these phone calls.

Diacritics
Checked again and there were some bad diacritics from MBG content and for some reason SI ones now looked fine for last few weeks. Emailed Keri and she said the whole thing was a bit mysterious. IA was determining encoding by looking at the leader. Susan’s understanding had been that each library specified the Z39.50 configuration when they first started working with IA. KT said some of SIL’s leaders are incorrect. Bianca has followed up with Jude and we are waiting for IA to investigate and schedule a time for discussion.

Author Names
Susan shared an article on author names: http://lib.dr.iastate.edu/cgi/viewcontent.cgi?article=1014&context=refinst_pubs Community is all over the place on how best to handle. Susan’s personal preference would be to have bother normalized/preferred name and name as published. Author names are on our longer term tech wish list. No action items at this time.

BHL Move Update
Still waiting to hear back from Office of Contracts. We’re in a holding pattern for now and still looking at a March launch date.

Could use a different url with an si domain to accommodate terms of service issues but that would impact analytics etc. Not something ready to pursue.

EABL Update
Susan and Mariah recently visited UF and they’re working with a tabletop Scribe.
However, they don’t have any MARCXML records. Susan would like to start by talking to Joe DeVeer about what procedure they need to get MARCXML in. Then talk to UF about doing that.
Know of 2 different ways to retroactively get MARCXML, at AMNH, they give Jude the files and bib records, he pulls the MARCXML and adds to IA. Another procedure would be to do it all in BHL, it involves a couple of harvest cycles.