FRIDAY--Jan. 20

 

9:30 -5:30       Bigheads (Technical Services Directors of Large Research Libraries)

http://www.loc.gov/library/bigheads/

 

            Casalini has been trained in cataloging and NACO. Bib records from them cost; NACO is free. Library of Congress at first decided to not distribute Casalini bibs with the rest of their bibs. OCLC has also been talking with Casalini and has agreed to become a partner.

            Harvard is paying Harrasowitz to add 653’s in English and German for $4.00. They feel it saves time in subject analysis and the records are more searchable in the OPAC while the book is in backlog for cataloging

            Stanford is using YBP (Yankee)’s Yankee Provisional Plus” – they have to pay for it but they have saved staff resources and sped up the process. It cuts down on “handoffs”. They are working with other vendors to obtain full or partial cataloging and processing

            Value – how do you measure? – current costs against currency of service

            Maintaining this process – will we have consistently high level bibs and NACO is less people are inputting or updating these records in the utilities?

            One library has used YBP shelf-ready for 9 years and are very happy with it

            University of Minnesota hopes to expand their YBP “plus”

            Columbia doesn’t review the cataloging. Another library reviews for series and call numbers and duplicates but otherwise does as much automated processing as possible

           

10:30 -5:30     MARriott RiverCenter  -- Salon I

CC:DA Discussion of Draft Part I (RDA)

 

Friday’s meeting was to discuss the draft of RDA Pt.1 as a whole and to look at usability.

Issues discussed:

  • There is still redundancy
  • Non-text is addressed differently than text resulting in inconsistency of rule presentation
  • Numbering is generally presented, but applies only to serials
  • Scale is mandatory but is not in ch. 1
  • ISBD being completely separated results in text no making it clear what the end result should look like and you have to look outside the rules – an extra step for catalogers and perhaps ILS vendors’ presentation
  • Some references take you to another rule that reads the same as what you started with
  • If JSC is committed to creating a document for other metadata, there is still a lot of work to do
  • Terminology and definition of terms is not consistent
  • If it is doing FRBR tasks, they are not being done per chapter – they are mixed. However, the rules are intended to be used online with linking rather than read beginning to end
  • Background, introduction, etc. should be clearly differentiated from the rules with numbering
  • 2008 date is publication date – deciding on text will be in 2007 therefore training needs to be done so in-the-trenches catalogers are ready
  • Problem with separating ISBD is that it is also a content standard and may not always match the content piece in RDA
  • Too many options to the point that resulting records will differ significantly
  • Not always clear if the rule refers to the “work” or a “manifestation”
  • Looks like less brackets for print, but more for non-print – that doesn’t make sense
  • Where do “work” and “expression” get addressed? – it seems manifestation-based
  • A workflow chart would be helpful
  • Goal mentions “extensibility” but it doesn’t show up in the rules well nor differentiate “for use by librarians” – e.g. Dublin Core basic vs. Dublin Core expanded with sub-elements
  • Content object model seems lacking – should be option to use application profiles in combination with other content standards – e.g. Dublin Core plus application profile and IEEE Long
  • Introduction seems divided between analog and digital whereas ch.1 refers to tangible and intangible
  • Single vs. multiple record approaches aren’t addressed
  • Reproduction changed from our norm of cataloging with original and adding secondary information about the reproduction
  • RDA doesn’t recognize that data may result in data storing different records in your ILS – e.g. a way to do multiple forms may be to use Holdings records

 

Chapter 1

At lunch several groups met.

Serials group:

“successively issued resources” – an unhelpful phrase

  • Mode of issuance vs. type of resource is confusing
  • If we mean multipart, can’t we start there and move through the rules for serials or something in the web that will pull serial stuff together?
  • Description varies for integrating resources vs. journals – i.e. one is based on first and the other on most recent
  • 1.2.3 and 2.3.1.11-12 talks about changes in title but doesn’t actually say when to make a new record; it doesn’t address switching formats

Unpublished:

RDA has not dealt well with materials that are not self-describing – i.e. no title on a web page; unnamed image)

 

Chapter 2

  • 2.1.1 – “separate” in last paragraph needs to be clarified
  • 2.1.1.1 -- #2 has two issues: 1) maintenance over time for a serials, 2) some things are numbered but not sequentially, e.g. topographic maps, and some are sequentially numbered, but not issued sequentially
  • 2.2.—missing concept: described by external source, containers, etc.
  • “preferred” – library community understands this to be “most important” whereas other constituencies may think these are “just nice”
  • 2.2.2 doesn’t say what to do if multiple things listed occur or none of the things occur
  • Parallel titles don’t always stay in order

 

7:30-9:00PM   Marriott Rivercenter  -- Salon D

FAST Subcommittee

I took minutes for the Chair who will prepare them.

 

SATURDAY--Jan 21

 

8:00-9:00        MARriott RiverCenter  -- Salon J

Ex Libris – Open URL – Haystack in the needle

 

Ex Libris demo’d a new product, Primo. The presentation began by showing how the online environment is changing for users.

Homogeny – the web experience is generally the same. Amazon brought in chat – what people think about a book. There are portals, e.g. Yahoo news, shopping, etc. You can be the “pro” and do your own travel arrangements. The “I” – Ipod, Ifactory, etc. – kids are carrying digital libraries around in their pockets – my music, my articles, my email. Blogs – we all can publish and communicate. Wikis meet a desire to find a trusted source. “metadors” – ability to let go of bookmarks and access them anywhere; you can classify yourself. You can set your “tags” – remember something for later recal. Flick’r – your photos. Contextual commentaries – e.g. facebook, my “space”. What’s happening? Relationship management, self management, bypass navigation, concensus vocabularies, classification exposed, personal GIS (mapping), personal publishing, develop your own portal.

Challenges to the library. Searching the OPAC – search, browse, rank – what’s the difference? Users are now experienced – they are expecting Google, my iPod, etc. Yet, users cannot find what they need without help.  The role of the library is to become a vital source of information and services. Make end-users benefit from services: bring content and services to users – not users to content; content cannot, should not be in a single container.

Strategies:

Help libraries focus on core work

Easier to maintain, reduce cost of ownership and provide business tools to make informed decisions

Focus on the user – provide systems and services that will expose content and services to users when and where they need it in the way they expect it

 

Primo

  • Focus on the user experience
  • New solution to address user expectations
  • Put user in control without the library losing control
  • Architecture – decouple end-user discovery from back-office functions from data creation and maintenance
  • Primo is a piece of their strategy for new/next generation of library service
  • Primo is an end-user tool
  • Cuts across collection types
  • Diverse data sources – Ex Libris and other vendors
  • Applicable to local collection OPAC and remote resources together
  • “fun, fast, forgiving”

 

Structure

  • Interoperate with any environment you chose – your institutional portal
  • Simple search box with dropdowns below if you want to limit
  • Left side is result list and right side are faceted results to check and bottom suggests other searches
  • Results can come from SFX knowledge base or your OPAC
  • Multiple version – FRBRized view – groups multiple editions
  • Includes title page covers, even for journals
  • Gives options like: location for a book – available; reserve – if checked out
  • SFX is imbedded in the journal homepage view
  • Book displays – can (if choose enrichment) see table of contents, cover, reviews
  • Option to “tag” for yourself or put on e-shelf
  • Images use jpeg 2000
  • Sign in / sign out at top right
  • Right, lower – refine results
  • Has faceted browsing lists are that presented based on cross references (preferred / non-preferred terms) to related terms from thesauri (LCSH or whatever you use) – users don’t have to guess the “right” word
  • Has a “did you mean?” function
  • Primo works with any harvestable database
  • Primo gives fast searching
  • Primo enriches information for user
  • J2ee java based

 

  • Plan 3rd quarter delivery
  • Looking for partners (testers)
  • “harvestable” – uses pipes to funnel in data from any open source; each pipe wil be normalized to be used
  • Hope to make it easy to manage; they will give you tools to build in more resources
  • Should be able to harvest local stuff (ContentDM)

           

Randy and I talked with Gary Johnson of SDLN about SFX. Gary said the cost of SFX was almost half the cost of Serial Solutions. SFX was fairly easy to set up. Metalib, is somewhat harder. Both SFX and Serial Solutions have bib records. (Serial Solutions said there is an extra charge for their bibs)

 

10:30-12:30      HCB Gonzales Convention Center – Room 208

                        ALCTS Cataloging Classification Research DG
 
Tami Morse (CSU) – trying to create FRBR from their OPAC data
o        FRBR seems to gather things pretty well, but not everything
o        OCLC found 86% of records could be FRBRized (i.e. have needed data elements)
o        Questions: is CSU data robust enough to support FRBRization? Will the research areas on campus benefit from FRBRization? How much manual work will be required?
o        They looked at how other libraries built algorithms. OCLC started with authority records and built keys to bib records. 
o        Mini bibs, bibs from other sources, changes in cataloging standards affect the quality of the records causing inconsistencies.
o        They did a test and analyzed the data and their tool tester. Testing against PA classification, 88% were single bibs. She didn’t think 505s were consistent enough to create a key (what about enhanced 505s?) Translations are hard to distinguish.
 
Glenn Patton (OCLC – FRAR)
o        Goals: 1) functional requirements of authority records, 2) feasibility of International Standard Authority Data Number (ISADN), 3) liaison to related groups
o        ISADN issue: are they creating a number for the heading or the authority record. Focus is shifting away from a single form of an entity to multiple forms per needs of each institution. Also, shifting from sharing actual records, to “intellectual” sharing.
o        FRBR model (see handout). Defined 2 types of users: 1) librarians, 2) patrons. User tasks: 1) find, 2) identify, 3) contextualize, 4) justify
 
Lois Mai Chain – FRSAR (Marcia Zeng is chair)
               FRSAR – Functional Requirements for Subject Authority Records. FRANAR (FRAR) and FRSAR are functional requirements for access points. FRBR entities: concept, object, place, event
 
Ed O’Neill (OCLC) – FRSAR

            FRSAR is the group 3 entities – define functional requirements for subject authorities to meet user tasks. Need to identify user terms and methods of use of data, e.g. cross-references. We need a standard communication format we all can agree on to share information. Implementation by vendors can vary.

 

12:30-1:00        HCB Gonzales Convention Center

 

            Ex Libris booth – talked with Maida Ruben about SFX – very helpful.

Ex Libris can house data on their server for just 3 libraries – it would be easily portable to different server if ODIN wanted a full implementation. Ex Libris can set 4 instances 1 per UND UNE UNF and state collection. ExL can send a person for a day to help you set up. We can extract comma delimited files and bring into SFX. SDLN said SFX was easiy to work with, but Metalib harder – Maida said the same thing. We would be putting SFX button on bibs and forget about trying to maintain them on bibs. I should be able to find correct ISSN’s in the Knowledge base – another problem ABC always has.

 

1:30-6:00        Marriott PLAZa San Antonio  -- Hidalgo BR A/B

ALCTS CCS CC:DA – Liaison      

 

JSC

  • RDA was made publicly available along with other documents (principles, prospects, FAQ); a listserv is set up – RDA-L
  • Comments should come through CC:DA or JSC’s web form for comments. Comments will not be considered from RDA-L
  • Outreach – Marjorie Bloss has been hired as a manager
  • Strategic Plan: goal 3, #3 – to be independent of format, system, … to communicate or store data
  • Objectives:
    1. design of RDA
    2. functionality of records when you use RDA. Note: the way a resources presents itself vs. accuracy  - JSC is favoring recording what you see and adding notes to clarify or add additional access points
  • Member question: “follow common practice” – just what does that mean?
  • Policy: the Policy documents how JSC does its work and it is being done differently to get RDA published. Once it is published, we will return to the old way of reviewing rules.
  • Examples: if there are examples you would like to see in the text, send to Jay Weitz

 

Library of Congress

Report: http://www.loc.gov/ala/ala-winter-2006.html

  • CDS products are moving in the direction of being PDFs
  • Z1 670 includes how to use URL
  • LCRI will die with AACR, but a new took for RDA will emerge with cataloging decisions to includes rules and MARC21 application

 

Task Force on Digital Media

What principle should be used to guide us in determining extent (300)? What is essential to the user and what is readily available to the cataloger may be in conflict – it may be hard to find the information. If in doubt if it is “essential” include it

 

Digital graphic representation is now in 3 rather than 4. It will be a specific application of a general data element.

 

Task Force for the publication, Differences between, changes within

 Addressed two questions: 1) is it realistic to try to revise in between AACR and RDA? And 2) is PDF an adequate means of publication?

 

Regarding Guidelines for Cataloging of Record sets: Reproductions (Microform and Electronic) and Original Sets, it was decided there is still need for such guidelines.

 

SUNDAY--Jan. 22

 

7:00-9:00        MARriott RiverCenter – Salon G-I

                        OCLC  breakfast

 

There are now 54,000 libraries in 109 countries using OCLC. Openly Informatics has been acquired. Six reasons to contribute to WorldCat: International resource sharing, collection analysis, group cataloging, open WorldCat on the web, FRBR, Unicode supports. WorldCat will have FRBRized results in 2006. Next Space – OCLC’s new newsletter. Union listing will change in February. Disseration Database will be on FirstSearch. Working on Content Cooperation pilot. Remote Circulation pilot – deliver books to homes. ContentDM – harvesting free – should UND discuss? (Got person to email – not sure about FAST – would they become 650 7 $2?) Open WorldCat partners: As Jeeves, Google, Yahoo, Alibrs, Abebooks, Book Page, Biblio. 95 million clicks from partners to local libraries. Opening a wiki-like user contributed content pilot for book reviews. E-serials pilot – set holdings for e-journals from partners including SerialSolutions, Ex Libris. OCLC Terminology Services – taxonomies can be brough up during a cataloging session – MeSh, Dublin Core, gsafd. Browse Dewey – check Office of Research page to see how it works. Looking at using “tags” that you can add on the web to insert Dewey into that type of environment to categorize material and OCLC could utilize it. 

 

10:30-12:30      MARriott RiverCenter –- Salon D   

                        OCLC Connexion Users Group   

 

  • Statistics reminder: a link can be found either from the Connexion web links or the Connexion home page. New – all authorizations will be on one page.
  • Holdings update by OCLC number – can type into a box or import a file from notepat text file
  • Batch – now a search option, e.g. can apply default constant data to all searched records.
  • Indexes in searching – can customize the list you see; material type now in search screen; can use their default or add to the list with “modify”
  • Truncated list – now has “held” and OCLC number; can customize – right click – list setting, then add or remove or change order
  • Online constant data is per authorization
  • Edit – insert from cited record – if you know the OCLC number – in inserts a whole field; works on 76X-> fields
  • Unicode – at bottom of export box can check MARC-8 or Unicode. ILS needs to also be able to use Unicode (figure out how to get ODIN Aleph set right)
  • User tools now have numbers, not just numbers
  • Adding to foreign OCLC, you must use MARC-8 so under “Edit” you “verify” MARC-8. It will mark in red any bad character.
  • CKJ dictionary – can use to create records with two lines per tag – click “Link Fields” to create the brackets to hold the tags together
  • Can change complete interface language under “International”
  • MARC update (see handout) – May/July timeframe for:
    • “I” for integrating resources
    • New fields 031, 258, 698
    • Privacy indicator
    • Character set will work. Right now some are available for export but can’t update
  • Extracting metadata from websites – future development
  • Digital archive – upload to OCLC by adding a URL so your digital materials you catalog can be added to OCLC
  • OCLC Terminologies Service – no charge; need Microsoft Office pane to open at left; free acess thesauri will display in a browse list
  • E-serials holdings – can synchronize OPAC with WorldCat – testing with Ex Libris
  • Subscription pricing – once on it, PromptCat, Bibnote, Z39.50 cataloging through local system is free
  • Setup guide – help for customization
  • Keymaps – where I can put what I want my “function” key to be
  • Use Cntrl-tab to switch back to bib
  • Constant data doesn’t add to a field, it only adds fields; to add to a field use Textstring
  • Textstring – can be put on a keystroke – simplified constant data; inserts text and leaves cursor at end; check “assign keystrokes” to see what is currently assigned first; enter text with space for no indicator, e.g. 590  Text; can do several fields on separate lines:
      • 590  Local note
      • 949  Text $b Test
      • 690  North Dakota author
      • To make a blank field, use the pipe, e. g. 590 |BLANK|
      • For Fixed Field, use * to not replace what is already in the record, e.g. to keep ndu in Cntry, use ***

 

1:30-6:00        MARiott RiverCenter -  Salon L/M

LITA/ALCTS Authority Control in the Online Environment IG 

 

OCLC Terminologies Service

  • OCLC Terminologies Service is available to OCLC subscribers.
  • Use Microsoft Research Pane in Office 3 and with Internet Explorer 6
  • OCLC will be searchable and display in the pane while the center pane can be ContentDM or Connexion
  • LCSH Children’s will be included – could search there for ODIN

 

Library of Congress – Ann della Porta

  • Catalog now uses Unicode and includes Hebrew, CJK, Cyrillic, Yddish, etc.
  • Local libraries need to move to Unicode
  • Wait for the “death date” announcement to start changing authority records
  • LCRI 1.0G1 – accents – start using Feb. 1, 2006 – new way will be in Desktop
  • 670 $u can be added when necessary
  • Some authorities are not being distributed – those deleted and some with diacritics. A deleted record would still be in OCLC but not in LC
  • LC is still inputting with MARC-8 plus a few characters (13), some Cyrillic, etc.
  • Checkout Mao Zedong to see 880 and 440 with Chinese

 

OCLC MARC update – Glenn Patton

  • New fields will start in the Browser May/June, then later to the Client
  • Field 024 – other standard identifier
  • Field 031 – musical incipits
  • Field 670 $u
  • Integrating resources “I”
  • Special characters `_^~{}?(spanish)iBE0(degree)@(copyright)p(production)#
  • Unqualified personal names – will strip $eu4, validate, then re-assemble
  • RSS feeds – watch for

 

RDA overview – Jennifer Bowen

Main entry becomes citation in an effort to correlation with other citation manuals. There will be citations for related entries – series, analytics, works, expressions, manifestations; will include uniform titles.

 

 4:00-6:00         HCB Gonzales Convention Center -  Room 212A

NISO Standards update  

 

ISSN – Regina Reynolds

  • Medium Neutral ISSN = MNI
  • Principle tasks:
    • Broaden scope
    • Clarify ISSN assignment
    • Establsih ISSN user group
    • Establish new ISSN data distribution methods
    • Do PR
  • Multiple ISSN challenge:
    • One for all or many for many?
    • Embedding in DOIs, etc.
  • Assignment of MNI
    • The first assigned IS the MNI
    • All Will have ISSN plus MNI for current, ceased, in one or more versions
    • In 024 of each record in cluster of records related by 776’s or 022 with new subfield? – first need to get approval of the idea – 024 would be the same in all bibs with 022 being unique per medium/format
    • Example: doi:0.1038.mni.0028.0836
  • Proposed new product – ISSN data distribution and lookup service; still a subscription; collocation of related ISSN’s would be in the lookup service

 

Rights expression – Dnise Troll Covey

  • Trying to figure out how to modify rights management set for the entertainment community for use by the library community, i.e. deal with copyright
  • Decided they needed a glossary to make sure communication was clear when using terms
  • Needed requirement specifications to align functional requirements from multiple groups. They found it very difficult because there is so little commonality in in the arena they work or they focused on data or users or on technical data so that wasn’t the same. So, they decided instead to write requirements based on roles – fights holders, rights grantors, users, interpreters, mediators, enforcers.
  • Extend ERM initiative to more communities
  • Considering using CDL’s (Calif dig lib) document on licensing and copyright
  • Solution will: a) assume rights are gratned unless specifically denied, b) combine licneses and enforcement technologies, c) provide clafity and ambiguity, e.g. you can make a reasonable number of copies, d) NISO works in standards – they already have EdiTEUR, ONIX, etc.
  • The difference is private law contract vs. common law copyright

 

NCIP – Brenda Bailey-Haier

            NCIP is being tested with Ex Libris; some other vendors have implemented. Next meeting will be hosted by Ex Libris in Boston. http://www.cde.state.co.us/ncip

 

NISO strategic direction – Jan Peterson and Oliver Pesch

 

 

6:30-8:00        MENger Ballroom

Ex Libris reception   

 

I visited with Becky Bell and Gary Johnson. I discussed Primo and authority control in Aleph with Stephen Hearn.

 

           

MONDAY--Jan. 23

 

8:00-12:30      La MANsion del Rio  –Iberian BR A/B

                        ALCTS CCS CC:DA  -- Liaison

 

ALA publishing / Don Chatham:

  • ALA hopes to develop a webinar to bring a demo to a larger community
  • Need to hear what catalogers do and why they do it
  • Structural elements:
  • modes – full, concise, customized
  • interfaces –  1) search/browse, 2) smart sheet, 3) step-by-step
    • search/browse – dropdowns, heading captions, examples, text; popup examples, mouseover for definitions
    • smart sheet – chose from work sheets, e.g. by RDA, ISBD, MARC21; provides example of that element with RDA button to display rule; can be used in LIS cataloging class or training
    • step-by-step – guide through data creation process of a record; popups, hyperlinks, mouseover
    • customize: build your own context by exclusion or inclusion; context – need “bread crumbs” to back track several levels wherever you are, even from popups; can save session; show where I am in TOC

 

RDA discussion:

  • There is no structure in the rules that tells you to put 2 things together, so you don’t get told to put author statement after title; it just identifies each element needed
  • Part of it is ISBD but there is a little more needed – explain important relations – e.g. no collective title is title / author ; title / author
  • Not addressed – issue of repeatability and when relations need to be clearly stated
  • 2.4.0.3 – optionally instead of recording as appears, use heading – there would be no information viewing 245s for NACO work; Jennifer said an agency could decide whether to apply
  • 2.6 – numbering is an area where relationship needs to be stated
  • 2.6.1.3 – need to be able to record first number even if not in hand
  • 2.7 – publisher – consider in pt. 2 as access point rather than making OPACS try to create access from 260
  • 2.8 – again about abbreviations – let’s not
  • 2.8.0.3 – putting note in record to differentiate place rather than London, [Ont.] – can’t we put it with the place?!
  • 2.9 – “release” = publication, not distribution
  • 2.9.5.3 – last bulletin says “undated” but 2.9.1.3 says date unknown
  • 2.10.14 – series in different forms seems contrary to 2.10.1.2 and if you end up ppicking different forms, it might no longer match the main entry or authority

 

Jennifer Bowen’s list of issues:

  • MARBI/CC:DA session on joint working group for mapping RDA to MARC21
  • Sources of information needs work
  • 2.21 – take from anywhere in resource but what IS the resource?


MARBI report:

2006-1 – coding IAM 047 approved

2006-2 – X11 - $j approved

2006-3 – 506 in HOL approved with $2 to identify terminology

2006-4 – Unicode/MARC-8 – made a recommentaiton

2006-5 – ONIX fields

2006 DP1 – add 034 to authority format to support geographic searching will be a proposal

2006 DP2 – content alerts for visually handicapped; preferred a variable field, possibly 521

2006 DP3 – recording former headings when not appropriate for 5XX – LC will reconsider as another DP

2006 DP5 – ONIX coverage dates will come back as a proposal

 

Deutsche Bibliothek is moving to MARC21 and may be making requests for additions including record linking (similar to Aleph LKR)


FRAR / 4 – not really ready to comment until Part 3 is out

 

Next meeting at Annual

Fri. PM

Sat 1:30-5:3/6:00

Mon 8:00-12:30

 

1:30-3:30        HCB Gonzales Convention Center – Room 005

                        SAC -- General meeting

4:00-6:00        HCB Gonzales Convention Center – Room 005

                        SAC -- General meeting

 

FAST

SAC Fast subcommittee will have a program at Annual on Saturday, 1:30-3:30. I have been asked to submit our example of using Fast for our digitization projects for inclusion in the program.

Meeting names and uniform titles should be ready by summer.

 

MeSH pulled back it’s decision to separate facets in distributed records due to complaints by catalogers, but who really should dictate the decision? Catalogers or users?

 

Semantic Interoperability – I presented our report.

            I focused on the fact that we met all the parts of our charge and created additional source documents. The need to be flexible and the wide diversity of the projects we reviewed made it unrealistic to create a “best practices” document. Instead the Subcommittee created a document with guidelines and supporting background information. By using the prepared checklist and using information contained in the entire report appropriate to a particular agency’s planned project, an agency should be able to develop a viable project. Successful projects take a lot of work. The committee will do final wordsmithing and have the document ready for a vote mid-late February.

 

SACO

  • Classification proposal form is being worked on for web input replicating paper form
  • 54% of headings added to LCSH came from SACO participants
  • “specificity in natural language order” – reason for creating/using LCSH rather just keywords
  • Genre headings – can submit headings, but they will still be 650s and only when LC decides to make 650 genres into 655s will anything change; hope to have a list for review by Annual
  • Developing web-based training rather than in-person basic training at ALA

 

Northwestern University public pages has been updated with MeSH/LCSH mapped authorities through 2005

  

1:30-3:30          HCB Gonzales Convention Center  – 204B

ALCTS/SS Continuing Resources Cataloging Committee Update Forum - watch for reports  

 

Note:

GPO annual 2005 report at: http://www.gpo.gov/congressional/index.html

 

 

Note:  

LITA Standards Interest Group 

New standards updates: (4:00 PM – 4:40 PM)

a.       Standardized Usage Statistics Harvesting Initiative (SUSHI) http://www.library.cornell.edu/cts/elicensestudy/ermi2/sushi/

by Tim Jewell (University of Washington). Other members of the SUSHI group will be on hand to answer questions informally after the official meeting is adjoined.

Managing usage statistics for online content face both challenges and opportunities.

b.      License Expression Working Group

by Nathan Robertson (University of Maryland)

The group is jointly sponsored by DLF, EDItEUR, NISO, and PLS.  

c.       RFID standards and Issues Progress Report

by Dr. Vinod Chachra, CEO VTLS Inc and Chairman of NISO’s working group on RFID standards. 

d.      Vendor Initiative for Enabling Web Services (VIEWS) http://www.niso.org/committees/VIEWS/VIEWS-info.html

by Candy Zemon (Polaris Library Systems)

VIEWS is an initiative by vendors and library service organizations aimed at the enabling of web services between disparate applications used in libraries.

2.      ISBN-13 transition (4:40PM – 5:30PM)

a.       Library of Congress will provide its insights about the changes.

b.      Innovative (Theodore A. Fons) will review the requirements and technical challenges facing ILS vendors for the implementation of the ISBN13 changes in the Integrated Library System industry.

c.       OCLC will describe its current implementation of ISBN-13 and its plans for implementing more fully in 2006.