Approval of Minutes 2006 (Daniel, 5 min.)
Bible uniform titles (5JSC/LC/8). (10 min.) Per JSC April 2007 Outcomes: *
All constituencies supported removal of the bias inherent in the current uniform titles for the Bible, but there was disagreement as to the best way to do this [e.g., see 8/27/07 AJL position and other correspondence]. The JSC decided that some changes could be made for the first release of RDA, but that other changes would be considered later.
The constituencies will be asked to confirm that they agree with the following changes and that the expense of implementation is justified:
The Old and New Testaments will be referred to by their spelled out forms, not the existing AACR2 abbreviations “O.T.” and “N.T.”
Access points for individual books of the Bible will use the name of the book immediately following “Bible” rather than interposing the name of the appropriate Testament.
Access points in the form “Bible. Old Testament”, “Bible. New Testament”, and “Bible. Apocrypha” will be used to identify those parts of the Bible as aggregate works.
The JSC agreed at the meeting that an instruction will be added for sacred works identified as works of personal authorship to allow for the use of the name of the personal author as the primary element in the access point representing the work.
Hebrew-script access points
Discuss immediate future of Hebrew references in authority records (Joan Biella, 5 min.; hold for Sunday meeting?)
Ketiv male vs. Ketiv haser in MARC21 246 [and other fields?] (Yossi, 5 min.).
- Consider AJL maintaining its own Hebrew-script authority file (5 min., Bernie in absentia? Lenore? I need help with this one), that AJL endorse provision of Hebrew script 4xx and 8xx fields, in order to ensure access to series through original scripts.
ex.: 170 קטלוג (Muze'on Yisra'el (Jerusalem)) Consider use of NSDL Registry for Managing Hebrew-script controlled vocabularies, e.g., for Hebrew GMDs (Daniel, 5 min.)
(Just as background: ALCTS Task Force on Non-English Access: revised report, March 2007
)
Discuss changed vocalizations between the 1997 and 2003 editions of E-S (e.g. ra'yon/ra'ayon; mahazor/mahzor; ma'gal/ma'agal; ma'yan/ma'ayan; mahashavah/mahshavah/; optsiyah/optsyah) (Jasmin, 5 min.)
Volunteers for adding Hebrew-script captions to LC Classification schedules for subclasses BM and KBM (Lenore, 5 min.)
Propose that dates be allowed as additions to liturgical uniform titles? Esp. siddur and haggadah? (5 min.)
Propose setting off initial articles in title fields rather than using filing indicators (Nancy, 5 min.)
Communal notification approach for reporting errors in PCC records? Could we use Heb-NACO? (Joan to try to draft a proposal to hand out at the meeting, 5 min.)
LCSH subdivisions to bring out "scribal traditions", e.g., something similar to "Manuscripts, Hebrew--Yemen", but to indicate "Yemenite Hebrew manuscripts" rather than "Hebrew manuscripts located in Yemen". (5 min. Dan Rettberg, in absentia)
RLG and OCLC (10 min.)
Implications of JNUL joining WorldCat (cf. May 9, 2007 announcement from Elhanan Adler), and RLG being absorbed into OCLC
Hebrew script generation macro (Jasmin?), final endings replaced by an ordinary initial or medial form of the letter.
- Indicator code script-toggle macro?
Completed as of AJL 2006?
-
Treating introductory title words Kuntres, Maamar, etc., as we currently do Sefer. (Has this been taken care of completely?) [UPDATE]
-
Continue discussion on treating some piyutim (liturgical poetry) collections as uniform titles and others as form subject headings [UPDATE. a quick follow-up from last year, Peter Kearney?]
*JSC October 2006 meeting Outcomes: "JSC affirmed the role of the IME ICC draft Statement of International Cataloguing Principles as the basis for the cataloguing principles used throughout RDA". The "Statement of International Cataloguing Principles" (http://www.loc.gov/loc/ifla/imeicc/pdf/statement-draft3_apr06cleancopy.pdf), states that "Access should be provided in the original language and script whenever possible, through either the authorized heading or a cross-reference." (the second paragraph in 5.1.3. Language under 5. Access Points)