Entries in the Category "DMS"
DMS notes 3 August 2009
Review DMS website: https://www.ohiolink.edu/ostaff/tech/
Update from Tom Sanville
-- LAC and CIRM meetings. PsychINFO changed to pay-to-play. AP Photo may also go this route. Otherwise, all else will remain the same. Review of EJC licenses later in the year.
-- 13 percent decline in budget
-- ISI, SCOPUS separately. This may change. ISI expensive.
-- Deduplication on journals project (?). 20 years versus 2 years. How to use central money to fund this project. One issue: bound versus unbound journals.
-- Possible project: replace ex libris tool with different metasearch engine.
-- Catalog ILS architecture project.
-- See "final report" from link below.
-- statewide resource sharing project. Migration to non-III centric system. Organization of cat architecture effort first.
-- ILS system for depositories; how to set this up. Unified III system for depositories. Capital request not yet made.
-- Insecurity of losing staff at individual institutions, with central systems.
-- Who will do database maintenance at individual institutions?
Update on Inventory of Cataloging Expertise
-- 95 invitations sent out [we have NOT yet responded, but I will soon]. 41 responded.
-- Timeframe: August or September. Next Spring: implementation.
-- tabs: potential need experience with OCLC products and services, need experience with OCLC products and services, have subject expertise, need subject expertise
-- subject expertise at institutions recorded. Question on what institutions are willing to share their expertise, or do on contract.
-- OCLC products and services: CONTENTdm, Regular Enhance, PromptCat Profiling, Batch Reclamation, WorldCat Local, Connexion Client, Connexion Browser
-- PCC Institutions in: BIBCO (OSU, Oberlin), CONSER (Univ. of Cincinnati), NACO (Oberlin, OSU, Kent, Univ. of Cincinnati), OCLC National Enhance (many), SACO (OSU)
-- Needs: DC Metadata, EAD, authority control, e-books, educational metadata, maps, MESH, rare books, scores, streaming videos, VRA, series authority, mixed material, LCSH analysis, e-maps, gov docs, MODS, ETDs, e-content resources, establish LCSH
-- Have expertise: print monographs
-- Technological expertise needed: automated authorities, batch load, ERM expertise, MarcEdit, NLM Doctrine, Perl expertise, serials holdings, URL resolvers, XML environment
Group Technical Services TF2 recommendations and next steps (http://platinum.ohiolink.edu/dms/GroupTS/index.htm ; click on "Final report")
-- pilot projects. Possible hubs.
-- issues regarding one catalog system.
-- coalition of the willing, for now
-- hubs not as pilots but as another way to do work
-- RDA April 2010
-- OSU as test site. Nov. - Jan. 2010. Purpose of test is in part to see how much time and money is necessary for future training.
-- Suggestion to use ONET as training site.
-- 3 field changes: http://loc.gov/marc/formatchanges-RDA.html
-- RDA site: http://www.rdaonline.org/index.html
Catalog/ILS Architecture Steering Committee: update and discussion of recommendations
-- PCIRC first level.
-- Equinox. Alternative to III. Vendor using open source
-- Next, ERM, batch loading
-- Evolutionary project, not 2-3 years.
-- implement PCC.
Provider-neutral standard for electronic monographs
-- reproduction note currently exists. URL exists.
-- batch reclamation.
-- dups, 019 field
Electronic Resource Management Task Force - discussion of charge and formation
-- implementing the ERM module.TF examining issues and best practices,including new record structures,codes, and specifications, standards, workflows
-- use of the module for user access
-- use of the module for staff access and management of electronic resources
-- examination of local needs and practices
-- contribute to the development of functional requirements for a new catalog system so that electronic resource management functions are fully integrated into the initial design.
-- critical examination of local needs and practices and the implications for the OLINK central catalog
DMC-DRC (digital media center --> digital resource commons)migration and catalog records
-- all old DMC material has migrated. URLs in catalogs need to be updated. See DRC web page for chart.
-- CSU counts database as database, and use serials solutions for ejournals. Serials solutions is not one aggregator database.
-- how to count current serial subscriptions. Do you count EJC titles? Most, no.
USC proposal re: links from catalog to GoogleBooks
-- preview, more information, full text.
-- Suggestion: say "snap shot" instead.
Miscellaneous
-- OU contribute all serials solutions to central. All are 956.
Update on RDA testing (Magda El-Sherbini)
-- http://blog.zsr.wfu.edu/pd/category/2009-ala-annual-chicago/
Cooperative collection/cataloging of government documents (Question from Paul Kobulnicky, YSU)
"Here is the original question from Paul. I think this issue overlaps at least DMSC and CIRM, and possibly other committees as well. If we have time to kick it around a bit Monday, great. If not, I'll throw it out again for email discussion."
"Jeff [Trimble] and I were just talking about Federal Document records in our III system and I was wondering if anyone had started to talk about a coordinated, simplified State-wide governement document collection with streamlined record keeping in the Central catalog and associated web access or P-circ access for print? Why are we all loading Marcive records and storing materials that are really very lightly used? Can't we centralize this at great savings?"
OhioLINK DMS Meeting Notes June 2, 2009
Database Management and Standards (DMS) Meeting, June 1, 2009
Discussion of DMS strategic actions and role of the committee in the consortium
a. Review "Action Plan" presented at June 2008 meeting (attached), which was based on analysis of DMS-related implications from all 16 "Visioning task
force" reports. What's been done; what needs to be done; what's going on elsewhere? (Margaret - report on the survey can go here)
b. Review expected recommendations from Group TS TF2; CatArch, and Discovery Layer TFs (drafts not available yet, but many DMS members participated in the
TFs and can discuss).
-- Expertise. Most important item.
-- Electronic Resources Management (ERM) Task Force to be developed within DMS
-- YBP approval plans coordination. Twenty percent discount is in jeapardy due to fewer books being purchased. Shelf-ready books. Idea to have an OLINK
account, for better coordination.
-- Training should be coordinated via ONET. This goes across OLINK committees
-- Foreign Language Acquisitions. Should be low priority. Materials purchased is heavily English-language. Not a widespread issue.
-- Binding. Not a widespread issue. HF Group -- do we use this?
-- item add: batch cataloging and batch loading
c. Revisit December proposal to LAC re: support for consortial resource cataloging, in light of TF developments. (Also attached)
d. Discussion of the role of DMSC in the consortium, and what the committee should be doing going forward
Depositories will have their own III system. Materials sent to regional depositories will become the depositories' property, not the institution that sent
them. In other words, no return policy. You would have to interlibrary-loan the material. Issue: what to do with records in contributing library's system.
Strip them from OCLC.
ACRL statistics ask or shared ownership.
Cataloging task force. You have a long time to contribute records to the central catalog. You have the option to contribute records.
ONET is going out of business (??)
Write local practices policies, and send them to central for documentation. (e.g. data one moves around, past practices that have been superseded).
Tom Sanville
OLINK budget. $5 million. from $7 plus million. 7.5 percent cut in EJC. Cut is equivalent to cutting Elsevier.
CAT-ARChitecture. central catalog. one bib concept problematic. Desire is to have what III has and more. Cf. OPAL.
Individual libraries should discuss these documents.
Reinventing OhioLINKand DMSC document. discussion
-- disconnect between DMS and DRMC.
-- disconnect between instit repositories and e-resources.
-- MarcEdit uses RDF for Dublin Core. No XSLT exists to go from MARCXML to Qualified Dublin Core.
-- approach YBP about statewide resource sharing
April 2009 Meeting Notes
Notes from the 2009 April DMS Meeting:
1. Tom Sanville
Future meetings at state library
2. 856/956 conversion
Records currently with 856 that need to be changed to 956. Suppress the record, edit it, then recontribute the record. Bring records in as "s" or "z". OCLC
looks at 9xx fields as locally defined. Make sure loader doesn't strip out 9xx's.
Suggestion: get rid of BCODE3="g" first. You could see what's happening with records in central, but you lose functionality of g
Change g to z
global update, insert 945, and take g out.
FirstSearch, etc. do not have RAv url's.
ABC-CLIO are _not_ OLINK
At Wright State, item records are made for all e-resources.
JSTOR 956's.
EJC. print records should not have "g" in first place.
RAVE URL -- proxy for OLINK.
Schedule with Anita flipping 956's.
Action item: Gather g's, convert to dashes (-). Instructions will be sent out to show people how to do this.
Then, 856/956 conversions will be scheduled.
Action item: Do NOT use "g" for new records.
3. Contribution of non-OCLC records; standardizing 001s
Means to avoid several different versions of same record.
035's must be moved to 001, if 035 is used.
For those that don't have load profile training
Add "1" in MarcEdit, before prefixes.
Add "1" for all non-OCLC records.
To contribute to central...
Look for Meg Spernoga e-mail with spreadsheet
Should be done retrospectively
Do not overlay non-OCLC with OCLC record
EBSCO files. Not locally loaded (??).
4. ETD
add gmd
245 $[electronic resource]
etc. etc.
add advisor? [79x] field
653 student supplied keywords, not LCSH
http://platinum.ohiolink.edu/dms/catstandards/etd.pdf
5. Chadwyck-Healey Cataloging
6. Naxos Cataloging
OCLC has given up on keeping up on new releases from Naxos
240 records in a year
7. Survey for inventory of cataloging expertise
Kent State. in progress.
8. NACO
Training already took place at Kent State.
OSU.
e-mail B. Strauss by Friday what from Tech Services has to be done locally.
rush cataloging
DVDs, VHS
special collections material
metadata work
stack maintenance
DMS Notes -- Feb 2009
Notes from the OLINK DMS Meeting, Feb. 2, 2009
1. 956/Bcode3 "g" - finalizing guidelines to allow all sites to complete conversion.
Use for current things we're working on.
Talk to Innovative if 956 does not display correctly.
Change from g to dash (-)
If you change from 856 to 956 in one step globally, something wrong happens. So, do a 2-step process
103422 – III PAGE NUMBER IN MANUAL
Amy at Kent. Mentally group records. First question: What products are ours? Then, figure out how to get at records
For OLINK pay-for-play titles, do NOT code as "g" but instead as dash
Pay-to-play should be 956’s.
Do 5,000 a day
Edit 956 in OCLC before exporting it – only if loader accepts 956.
Test with a ETD, using both 856 and 956. (local goes to UMI).
From Sept. 4, 2008:
Over the past several years, librarians have been working with Innovative to implement a new field -- 956 -- for institution-specific URL's for electronic resources. For example, a URL that refers to your institution's proxy can be used only by your patrons. In the central catalog, the 956 URL displays with institutional holdings, rather than in first screen of the public display. This is intended to save users from clicking on a URL that applies only to a different school.
Good examples of records with 956:
The art of the viola
Irish Women Poets
19th Century Literature Criticism
Cardozo studies in law and literature
Innovative has installed the software on all systems Release 2006 or above. The WWWOPTION for 956 is LOCALLINK_TAG. To turn it on locally, look in your test WWWOPTIONS file for LOCALLINK_TAG (probably under INN-Reach Options):
LOCALLINK_TAG=956
This WWWOPTION may be inactive. In character-based interface, if it is commented out #, un-comment it. In Millennium, if it is inactive, uncheck the inactive box to make it live. Move it from the staging directory to the live directory.
CATALOGERS: When 956 is "on" in your system, test it by adding 956 to a bibliographic record. If the record displays a URL in your local catalog, it works. Then, you can begin to use 956 for local URL's.
Our slogan "8 for All; 9 for Mine" means:
856: URL for freely available Internet resources that anyone in the world can access.
856: URL for ohiolink-wide resources, such as our electronic
journals, books, and videos.
956: URL for resources paid for by your library and/or available only to your users. These resources are restricted to your campus IP addresses or people who can log in to your proxy server.
2. Survey of OhioLINK cataloging expertise
UCin and OU to do initial test of survey.
3. Re-starting Chadwyck-Healy cataloging project - broadening participation
[see chart]. Proquest records are good records. Make a record based on proquest record, or just create a record.
ECTI. Cataloging done, but not contributed to OCLC and doesn’t have a unique URL. Cataloger needs to insert URL as 856, turn them into OCLC record. Then, create a file for other libraries, and contribute to central catalog.
Vendor-neutral monograph records? Bibco group.
Jeff to provide macros. Uses III loader to do processing.
4. Updates and discussion on Task Forces: Discovery Layer; Catalog Architecture;
Group Tech Services 2.
Discovery layer. Serial solution, oclc, index data, ebsco, etc. Work on federated searching. Encore product.
Open library environment project (OLE)
Rochester extensible catalog.
5. Cataloging non-OhioLINK electronic resources:
(1) If the vendor supplies OCLC records, the library can contribute these to Central.
(2) If the vendor supplies non-OCLC records, either suppress them from Central, or else modify the control number (001) in such a way that the records do not conflict with OCLC records.
(3) When contributing non-OCLC records, use a standard format for the 001, to avoid duplicate records.
(4) URLs that apply to certain subscribing institutions and not all OhioLINK libraries should be tagged 956.
e.g. ebrary books. Question: should we contribute them to central?
Records with prefixes. List of prefixes currently being used. What vendor records have you bought and what were their prefixes?
If you insert prefixes, you don’t need to suppress from central.
Loaders strip off prefix. Therefore, put a number before the prefix. Have a number, then 3-alpha. Run through MarcEdit before loading.
If you want to contribute non-OCLC records, DMS insists that you use a prefix (suffix), using MarcEdit. If you don’t do this, you must suppress.