- BSLWAC - mailman.xmission.com

Backstage - Not so FAST!
by Nate Cothran 01 Oct '13

01 Oct '13

In conjunction with OCLC's recent announcement of "adding FAST headings to selected WorldCat records", Backstage is also preparing to make these authorities match-able and return-able should you choose to have this done via our authority control processing. What this means right now is that the heading would need to be in this format for us to match against the FAST authority database: 6xx _7 ... $2 fast We would treat FAST subject headings similarly to how we treat other authorities from different genre databases. Both the 2nd indicator value of 7 and the $2 fast need to exist on the FAST subject heading. Please note that we do not have the capability (yet) to match against 648 subject headings, which are Subject Added Entry - Chronological Terms. A brief example of one of these records is: 001 fst01355873 148 $a 1914-1918 448 $a World War I Period We are working on getting the programming into place to handle these, but so far there only around 700 FAST authorities for these types of headings. The full FAST authority database that is now available comprises nearly 1.7 million authorities. Please let us know if you are interested in having us match your FAST headings against this new database. We are working on updating our collateral to reflect this. Nate Cothran Vice President, Automation Services 25 East 1700 South Provo, Utah 84606 Phone: +1.800.288.1265, ext. 697 Direct: +1.801.342.5697 nate(a)bslw.com <mailto:nate@bslw.com?subject=Automation%20Services%20-%20Inquiry> * www.bslw.com <http://www.bslw.com>

1 0

Backstage - Reports
by Nate Cothran 24 Sep '13

24 Sep '13

We are currently working on improving the base HTML reports that are generated and sent out with every Backfile or Current Cataloging processing. >From 2004 to 2012 we contented ourselves with having reports in HTML format only. Over some of those same years, we had requests to make the reports able to be sorted, edited, and generally rearranged. In an effort to address these requests, we developed an in-house solution to convert the existing reports to XLS. Now, nearly every report is also available in a simplified version (which may not always mean better) as XLS. But we are now revisiting the HTML reports. Our lead programmer has figured out a way to improve the efficiency and usability of these reports. In fact, I have attached a sample of the latest prototype for the revised HTML reports (see: R07 attached). This new functionality allows you to sort the results on nearly anything (control number, tag, field data). You can also search through the results for specific fields or headings that start with certain characters. It even finds results if they have diacritics (without requiring you to input the diacritics). Our philosophy with respect to reports is that we do not like to leave any stone unturned. If it is possible for us to report out on something, we elect to do so. Currently, we have in the neighborhood of roughly 90 separate reports (AC, RDA, Notification, etc). This can be wonderful for clients that love that kind of detail and view all of the different updates that have or have not been made to their data. It can also be overwhelming to other clients that may just be interested in a quick report that tells them the salient information with further access to these other reports when desired. So we are exploring the development of a single report which is comparatively brief (around 1 page), that provides a sort of executive summary of the process itself. The intent is to present you with a general overview of the process while also allowing you to dip into the other reports at your discretion. The hope is that this brief report would help satisfy those clients that are not interested in poring over our other reports and just want something relatively simple that gives an overview of the processing. And it might help our other clients that do make use of the other reports we have that go into much more specific detail. As we make more progress on this front, we will keep you updated. As always, please feel free to tell us what you like or don't like about our existing reports. If there is a way to improve the experience for you, we would love to figure it out with you. Nate Cothran Vice President, Automation Services 25 East 1700 South Provo, Utah 84606 Phone: +1.800.288.1265, ext. 697 Direct: +1.801.342.5697 nate(a)bslw.com <mailto:nate@bslw.com?subject=Automation%20Services%20-%20Inquiry> * www.bslw.com <http://www.bslw.com>

4 4

Backstage - RDA Enrichment Updates
by Nate Cothran 24 Sep '13

24 Sep '13

As a core group within our department, we meet regularly to discuss our RDA Enrichment service. During these meetings, we talk about three topics: 1. What isn't working 2. What needs to be added 3. What needs further review We are continuing to make improvements to the service, though at this point, most of them are minor adjustments to programming we already have in place. Sometimes, it does mean we are adding in functionality where it didn't exist previously. Our hope is that as you become ready to address RDA within your system, you gain the confidence you may need by knowing that we are continually focusing our efforts on this. Here are some of the RDA updates we've discussed and have either implemented or are implementing shortly (*please note that these changes will only happen for clients that have filled out the RDA online profile): * Change <space>p. to <space>pages in 5xx notes * Change pagespages to pages in 300 $a, 5xx notes * Only spell out bracketed 260 $a info if RDA; even with this one, there are specific instances where certain state abbreviations are acceptable in RDA * Do not change 260 $a n.d. (or N.D.) to date of publication not identified; this should only be spelled out when appearing in 260 $c, otherwise it should be expanded to North Dakota * Tighten up programming for adding 9XX Enriched to RDA enriched bibs; this was acting like our normal change stamps so we are looking into making sure this tag (if desired) is added specifically to records that have been enriched / validated by our RDA processing, rather than just to any record that has been changed due to processing * We have a client that wants their non-RDA bibs to have access points updated only, but also wants their RDA bibs to have enrichment + validation; we decided in cases like this it makes sense to use 2 profiles: o 1) non-RDA bibs: run Step 5 only (which addresses access points in RDA) o 2) RDA bibs: run all of RDA profile * For our GMD to (33X) CMC processing, we are addressing what happens when the resulting set of 33X fields contains 2 or more 'unspecified': o If all three 33X (336, 337, 338) contain 'unspecified' then we are choosing to not add any of those fields to the record and report on it (R132 - CMC Not Added); o If 2 of the fields are 'unspecified', then we will report those out; in conjunction with this we are replacing our R130 - CMC Added report with R130 - CMC Unspecified instead as we feel this report would be more informative than CMC fields that have been added * We are also looking at changing the priority of checking certain fields when it comes to trying to establish the most correct set of 33X fields. Currently, we search for existing values in the following fields in this order: 245 $h GMD, LDR-06, LDR-07, 007-00, 007-01, 007-xx, 008-xx, 300 $a. But we have discovered that, in some cases, the 2nd 007 may contain the better field from which to derive the 33X fields; however, our system only considers the first 007 at this time. So we are looking into a couple different options: o If two 007 fields exist and are unique, then we look for 007-00 'c' (electronic resource) first; o Or consider checking 300 $a first when 2+ 007 fields exist; o We are testing both scenarios to see which may be the better fit for processing * Add a rule to change 'cm.' to 'cm' for all records (not just RDA only bibs); the 300 field no longer needs to end in a period and we have had a few requests to have this changed * Move existing $e rda to follow last $b in 040 field; note: we are not adding $e rda at any point during machine processing My team may have more to say on these (especially if I have misinterpreted any part of the above!). Also, please feel free to ask any questions you may have about the information presented today. Nate Cothran Vice President, Automation Services 25 East 1700 South Provo, Utah 84606 Phone: +1.800.288.1265, ext. 697 Direct: +1.801.342.5697 nate(a)bslw.com <mailto:nate@bslw.com?subject=Automation%20Services%20-%20Inquiry> * www.bslw.com <http://www.bslw.com>

1 0

Backstage - AACR2 vs RDA Access Points
by Nate Cothran 06 Aug '13

06 Aug '13

We wish to bring to your attention a probable issue that you may face when it comes to matching or not matching your AACR2 access points against RDA authorities. For instance, say you have an AACR2 bib record with the following access points: 110 $a United States. $b Dept. of the Defense. 710 $a United States. $b Dept. of Communications. 710 $a United States. $b Dept. of the Defense. The 110 & 2nd 710 will match [n 79021946] and flip to: 110 $a United States. $b Department of Defense. 710 $a United States. $b Department of Defense. But the 1st 710 will not find a match and remains as-is: 710 $a United States. $b Dept. of Communications. So your processed (AACR2) record ends up looking like this: 110 $a United States. $b Department of Defense. 710 $a United States. $b Dept. of Communications. 710 $a United States. $b Department of Defense. This is the scenario that our clients are facing when Step 5 of the RDA Profile (link <http://ac.bslw.com/community/wiki/index.php5/RDA_5.0> ) hasn't been filled out. RDA Step 5 helps to prepare access points for better matching against RDA authorities. And it has this failsafe included: in the event of a non-match against RDA authorities, the heading itself still follows RDA cataloging standards. Of course, if your Library is not quite ready to embrace RDA and the changes afoot it may not make sense at this time to perform these kinds of changes to your access points. At the very least, we wanted to point out this potential issue and let you know that we have a remedy in place ready to go when you need it. For more information, please feel free to contact your project managers or myself at anytime: Nate Cothran nate(a)bslw.com Judy Archer jarcher(a)bslw.com Stephanie Hansen shansen(a)bslw.com Nate Cothran Vice President, Automation Services 25 East 1700 South Provo, Utah 84606 Phone: +1.800.288.1265, ext. 697 Direct: +1.801.342.5697 nate(a)bslw.com <mailto:nate@bslw.com?subject=Automation%20Services%20-%20Inquiry> * www.bslw.com <http://www.bslw.com>

2 1

Backstage - Authority Control for Digital Content (archived webinar)
by Nate Cothran 13 Jun '13

13 Jun '13

As an update from yesterday's quick post about a webinar that Jeremy Myntti (University of Utah) and I co-presented at this morning, I have another update. This is from Sandra McIntyre who was gracious enough to host the webinar, record it, and make it immediately available for those who may not have attended this morning. ------------------ From: Sandra McIntyre [mailto:sandra.mcintyre@utah.edu] Sent: Thursday, June 13, 2013 12:42 PM To: UALC Committee; MWDL Partners Cc: UALC-announce(a)lists.utah.edu Subject: [ualc-announce] Archived recording of webinar on Thu., June 13: "Authority Control for Digital Library Metadata" The archived recording of today's webinar is now available online. Jeremy Myntti from the University of Utah Marriott Library and Nate Cothran from Backstage Library Works gave a well-organized presentation on "Authority Control for Digital Library Metadata," discussing their joint project exploring how to automate the standardization of names and subjects within digital library metadata. The page also includes links to resources shared during the webinar. http://mwdl.org/events/authcontrol.php Please join us for future webinars and/or take a look at the archived recordings of other previous webinars from our Events page at http://mwdl.org/events/events.php. Thank you for your interest in the Mountain West Digital Library webinars! Sandra Nate Cothran Vice President, Automation Services 25 East 1700 South Provo, Utah 84606 Phone: +1.800.288.1265, ext. 697 Direct: +1.801.342.5697 nate(a)bslw.com <mailto:nate@bslw.com?subject=Automation%20Services%20-%20Inquiry> * www.bslw.com <http://www.bslw.com>

1 0

FW: Digital Tech Topics webinar on Thu., June 13: "Authority Control for Digital Library Metadata"
by Nate Cothran 12 Jun '13

12 Jun '13

Hello Everyone, We have been looking for opportunities to present our discoveries with applying authority control to a digital collection recently. This engagement (please see below) represents our first opportunity. I apologize for the short notice as this was one that came about rather quickly for us and we jumped at the chance to show you where we are with this potential service. The webinar is free to attend, open to all, and will be made available via a recording at a later date should you not be able to attend tomorrow morning. Jeremy & I touch briefly (towards the end) on linked data, though most of the presentation details our efforts with updating headings in CONTENTdm and providing greater access to those digital records. We hope to see you at the webinar tomorrow! Nate Cothran Backstage Library Works From: Jeremy Myntti [mailto:Jeremy.Myntti@utah.edu] Sent: Monday, June 10, 2013 2:33 PM To: Nate Cothran Subject: FW: Digital Tech Topics webinar on Thu., June 13: "Authority Control for Digital Library Metadata" From: Sandra McIntyre [mailto:sandra.mcintyre@utah.edu] Sent: Monday, June 10, 2013 2:26 PM To: UALC Digitization Committee; MWDL Partners Cc: UALC-announce(a)lists.utah.edu Subject: [ualc-announce] Digital Tech Topics webinar on Thu., June 13: "Authority Control for Digital Library Metadata" Mountain West Digital Library partners and other interested UALC library employees, Our next webinar in the series on "Digital Tech Topics" will be this Thursday, June 13. The webinar will be held online via Wimba web-conferencing. Those of you who have been wondering, "How do we start implementing Linked Open Data in our digital libraries?" will find this especially interesting. Please join us for this informative session! "Authority Control for Digital Library Metadata" Thu., June 13, 2013 11:00 am-12:00 noon MDT / 10:00-11:00 am PDT Via Wimba at http://my.uen.org/myuen/215484/ Presenters: * Jeremy Myntti, Head of Cataloging and Metadata Services, University of Utah, J. Willard Marriott Library * Nate Cothran, Vice President, Automated Services, Backstage Library Works The University of Utah's J. Willard Marriott Library <http://www.lib.utah.edu/> has been working with Backstage Library Works <http://www.bslw.com/> to come up with an automated solution for authorizing fields in digital library metadata to provide consistency and to improve access to collections. In addition to standardizing headings, this process will add links in the metadata records to the Library of Congress Linked Data Service (http://id.loc.gov) in order to incorporate some linked data best practices. This presentation will consist of an overview of the need for authority control in metadata records, the process that Backstage Library Works and the Marriott Library are working to implement, and a detailed look at the changes that can be automated through this process. Jeremy and Nate have suggested some background resources about Linked Open Data and authority control, which are linked from the MWDL web page about this event <http://mwdl.org/events/authcontrol.php> . Bring your questions about what this means for your digital library, or simply lurk and learn! Either way, we hope to "see" you on Thursday. Please feel free to forward this invitation to others. Sandra =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Sandra McIntyre | Program Director Mountain West Digital Library | Utah Academic Library Consortium http://mwdl.org <http://mwdl.org/> | +1-801-585-0969 | sandra.mcintyre(a)utah.edu

2 1

400 $wnnea
by Ted Waller 03 May '13

03 May '13

Should I be doing anything with the fields in authority records that begin 400 $wnnea ? These are the fields with the old name forms, and serve to identify headings in records that need to be changed to the new form (such as adding a death date). There appear to be two kinds: one with |5UtOrBLW indicating they were added by Backstage, and one without this subfield. The fields without the Backstage subfield are in the official LC authority records, the fields with the subfield are not. Should I be deleting any of these fields after the quarterly revised authority records are reloaded? At one point I thought so but now am not sure. Ted Waller Carlyle Campbell Library Meredith College 919 760 8381

2 1

Backstage - RDA vs AACR2 Authority Matching (Update)
by Nate Cothran 15 Apr '13

15 Apr '13

Over the last couple of years, Backstage created 7 different options for matching AACR2 access points and RDA access points in special ways. Then we started whittling that down as certain functionality became outdated or moot (e.g., 7XX-4 fields being "absorbed" into the authorities as 4XX fields instead). As of a month ago, we were down to two options. With RDA Day One already come and gone (April 1, 2013), we are now down to one option: 1. A bib record's access points will take the best match regardless of RDA (040 $e rda) or AACR2 status in the authority record. All of our clients have been "switched" to this new option for matching authorities, so there is no action required on your part in order to have this enacted. As always, please let us know any questions or concerns you may have. It is through you that we had developed the previous 7 options, as well as different ways of presenting the reports, and adding new options for RDA enrichment. Thanks, Nate Nate Cothran Vice President, Automation Services 25 East 1700 South Provo, Utah 84606 Phone: +1.800.288.1265, ext. 697 Direct: +1.801.342.5697 nate(a)bslw.com <mailto:nate@bslw.com?subject=Automation%20Services%20-%20Inquiry> * www.bslw.com <http://www.bslw.com>

1 0

Backstage - Phase 2 Authorities Update - 4/3
by Nate Cothran 03 Apr '13

03 Apr '13

Here is another update on the number of RDA authorities received from the Phase 2 distribution: NAF = 51,977 total authorities; 45,673 had 040 $e rda - (88%) Total RDA authorities for Phase 2 (so far): 376,148 name authorities This should represent the final update for Phase 2 authorities. Nate Cothran Vice President, Automation Services 25 East 1700 South Provo, Utah 84606 Phone: +1.800.288.1265, ext. 697 Direct: +1.801.342.5697 nate(a)bslw.com <mailto:nate@bslw.com?subject=Automation%20Services%20-%20Inquiry> * www.bslw.com <http://www.bslw.com>

1 0

Backstage - Phase 2 Authorities Update - 3/27
by Nate Cothran 28 Mar '13

28 Mar '13

Here is another update on the number of RDA authorities received from the Phase 2 distribution: NAF = 130,326 total authorities; 120,433 had 040 $e rda - (92%) Total RDA authorities for Phase 2 (so far): 330,475 name authorities Nate Cothran Vice President, Automation Services 25 East 1700 South Provo, Utah 84606 Phone: +1.800.288.1265, ext. 697 Direct: +1.801.342.5697 nate(a)bslw.com <mailto:nate@bslw.com?subject=Automation%20Services%20-%20Inquiry> * www.bslw.com <http://www.bslw.com>

1 0