| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

Minutes 2008

Page history last edited by Jasmin Shinohara 3 years ago

Home--Minutes--Minutes Archives

 


 

 

Date: June 22, 2008

 

Time: 9pm-10:30pm

 

Present: Elhanan Adler, Lenore Bell, Joan Biella, Beth Dwoskin, Joseph Galron, Janet Heineck, Aaron Kuperman, Daniel Lovins (outgoing chair, recording), Paul Miller, Stanley Nachamie, Jasmin Nof (incoming chair), Bernard Rabenstein, Daniel Rettberg, Nancy Sack,  Allan Satin, Daniel Scheide,  Marlene Schiffman, Avrom Shuchatowitz, Rachel Simon, Aaron Taub.

 

Committee Business

 

 

  • Daniel said that Jasmin, as the likely (now confirmed) chair designate, would preside over today's meeting, and that he would take minutes.

 

  • For future reference, Daniel will ask RAS whether:
  • a simple majority is sufficient to carry committee votes (Answer: yes, that's why odd number of voting members)

 

  • the incoming chair should receive a full copy of the AJL handbook, not just the section on this Committee (maybe)

 

  • [This point and the next came up *after* the meeting] it's OK to appoint a chair and vice-chair this year (probably yes).
  • Vice chair as likely successor

 

  • Assist chair in managing committee business

 

  • Time to learn the ropes

 

  • Make Joan Biella (or successor LC rep), member ex officio as is case with RAS president. Since Committee is charged to "act as a liaison with the Cataloging Policy and Support Office (CPSO)", this would help ensure the liaison relationship.

 

  • Cat Com Wiki

 

    • Daniel asked if pb wiki is OK, or better to switch to tiki wiki
    • For reporting bibliographic errors, actually, most of us seem to want to revert to email messages (HebNACO?)
  • Joan offered to look into Web form that would generate these messages

 

  • The question arose why catalogers aren't making changes directly to the WorldCat master record. Not yet "Enhanced" status?

 

  • In which case, why not use error reporting tool in Connexion client? Answer: with non-roman script records, it can take several months for a change to take effect, if ever.

 

  • Yossi asked about the the change notification feature in Connexion. But this is triggered by encoding level, not modification of record contents.

 

  • Aaron pointed out that, in the law and music cataloging communities, when a request is made on the professional discussion list, Enhanced status libraries make corrections on behalf of their peers.

 

  • Yossi worries about resulting increase in HebNaco traffic, since he has to approve each posting on the list. (He did say that it's no longer necessary to put his e-address on the CC line).

 

  • Daniel suggested that, for documentation anyway, e.g., vocalization changes in Even-Shoshan, the wiki is still preferable to email 

 

RDA

 

  • Lenore gave an update on the RDA treatment of Bible Uniform Titles.
  • Last year, JSC accepted a truncated version of the original LC proposal. The three remaining components are:
  • entering books (e.g., Genesis) directly under bible "Bible," rather than indirectly through a Testament

 

  • only using Testament headings to denote aggregates of books, not a particular canon, and

 

  • spelling out "Old Testament" and "New Testament," instead of the abbreviations.

 

  • LC is still considering implementation issues, e.g., should changes be made all at once as RDA is adopted, or rather in phases.

 

  •  Daniel asked if this means LC is now fully committed to RDA. At ALA Midwinter 2008, he heard Deanna Marcum say LC would suspend cooperation on RDA until  underlying FRBR model had been further tested (as recommended by the Working Group on the Future of Bibliographic Control)

 

  •  But sense at LC (based on internal communications and the the official LC response to the Working Group report) is that LC has resumed support for RDA

 

Authority Control

 

  • Daniel asked if there are rules regarding non-professional library staff contributing to the Hebrew NACO funnel

 

  •  Heidi responded that, from the NACO Funnel perspective, professional status doesn't matter. It's the participating library that decides who can submit headings. Expectation is that the library provides support for training, and that there is a tiered approach to gaining independence in names, titles, and corporate bodies. There's no need ever to move on to complex headings like pre-modern rabbinical names, but it's OK to do so if training is provided.

 

  •  In effect, the institution obtains NACO independence, not the individual. This could be problematic if, for example, a skilled cataloger leaves, and a new cataloger assumes the authorized NACO account but without the proper training and supervision.

 

Non-Roman script in authority records

 

  •  Joan gave update on the status of non-Roman script references in  National Authority File. She distributed draft guidelines for Hebraica and posted them to the wiki. These guidelines are provisional and will remain so until after records have been prepopulated by OCLC and reviewed by the community. Until best practices are codified, records with added non-roman script will be coded as having "unevaluated references" and given an explanatory note in a 667 field. After the review period, best practices will be identified and written up as LC rule interpretations.

 

  •  Daniel asked why a uniform title example in the draft guidelines includes "likutim" in Hebrew script, even though on the previous page it said not to do this. Joan said that this had to do with language adopted from Paul Maher's book, and that ambiguous or inconsistent details still need to be hashed out.

 

  •  Yossi worries about derivative, dual-script references being shown to our readers. Joan says this is a necessary consequence of the way our national authority file is designed (i.e. headings must be in roman script).  At some point we may have a separate Hebrew-script authority file (not just references) based on the JNUL file and the VIAF.  

 

  •  Yossi asked if LC will stop adding parallel Hebrew script access points now that they will be recorded in authority records. According to OCLC's David Whitehair, Joan said, the parallel access points will still be needed for indexing purposes, though  hopes to extract them automatically from the authority records.

 

  •  A new Subcommittee will monitor and report back on evolving best practices. Lenore suggested this group could start with Joan's draft guidelines and revisit them and recommend changes after new records have been studied. Yossi, Joan, and Jasmin have volunteered to serve on this subcommittee. Input from wider community will be encouraged via HebNACO and/or ha-Safran.

 

Bibliographic Description

 

  • Another subcommittee will study and recommend best practices for supplying standardizing Hebrew in bibliographic description; Aaron suggested that records which reflect these best practices should be coded at a higher level. Other attendees agree on principle, but worry about how to enforce proper coding; Yossi volunteers to chair

 

    • For example

 

  • ketiv haser vs. male?

 

  • nekudot?

 

  • non-filing articles and prefixes?

 

  •  Joan and Heidi gave a progress report on Judeo-Arabic romanization table.

 

  •  More difficult than anticipated.

 

  • Orthographies vary widely among regions and even within a single page of text. Less a language than a collection of dialects,

 

 

Action Items

 

  • Daniel will consult with RAS president about committee rules, and report back to committee colleagues (in form of parenthetical comments following bullet points above).

 

  • Jasmin will formally appoint subcommittees/task forces as mentioned above.

 

  • Joan will investigate using a Web form to support anonymous reporting of bibliographic record errors

 

  • Joan and Heidi will consult with Judeo-Arabic experts and determine whether feasible to continue developing romanization table

 

Home  

Comments (0)

You don't have permission to comment on this page.