Presentation on theme: "EURIG 3 rd Members Meeting Stockholm 19-20 September2012."— Presentation transcript:
EURIG 3 rd Members Meeting Stockholm September2012
Agenda: Day 1 am Welcome and introductions Minutes of 2012 Meeting and matters arising Membership/Update Survey Results 10:30 – 10:45 Coffee Reports of Working Groups Discussion of JSC Proposals – Aggregate Works 13: Lunch
Agenda: Day 1 pm Discussion of JSC Proposals – Internationalisation Election of the Committee 15:30 – 16:00 Coffee / Group Photo EURIG Activity Plan EURIG Members Meeting 2014 Announcements Conference Dinner
Agenda: Day 2 am Round Table Discussion Subjects in RDA (Alan Danskin) BibFrame (Alan Danskin) Linked Data(Gildas Ilien)
Welcome Introduction of the committee Introduction of members Housekeeping Minutes
Membership Current membership = = National Library of Iceland If you have not completed the membership survey, please do so before the end of September.
Membership Survey Responses (50%) Implementation: – Yes 8 – No 7 Replace current cataloguing code Interoperability RDA covers range of resources RDA too expensive FRBRization Cost effective Waiting to see how it works for others Not cost effective No suitable translation
Implementation Plans OCLC (Leiden)The Dutch FOBID Committee decided to move from RT to RDA in February Implementation in the GGC (Dutch Shared Cataloguing System) started afterwards National Library of SwedenA principle decision, no time frame set as yet Austrian Library Network National Library of Latvia2016 BNFWe decided to target the implementation of RDA, but under conditions and with no fixed schedule yet. Deutsche Nationalbibliothek2015 National Library of Finland2015 British LibraryImplemented 2013
Reports of the Working Groups Aggregates Group Music Group
JSC Papers 1: Aggregate works Papers for discussion 6JSC/ACOC/07 Compiler and editors of compilations 6JSC/ALA/Discussion/1 Machine-Actionable Data Elements in RDA 6JSC/ALA/26 Colour content 6JSC/ACOC/8 Addition of the Copyright holder relationship
ACOC/7 Compiler & Editor of Compilation Add new paragraph at Scope …Contributors also include editors of compilations, unless the selection, arrangement, editing, etc., of the content for a compilation effectively results in the creation of a new work. When this occurs, the person, family, or corporate body responsible for compiling the aggregate work may be considered to be the creator of the compilation, see
ACOC/7 Compiler & Editor of Compilation Change to Amend Recording Contributors …Record a contributor by applying the general guidelines on recording relationships to persons, families, and corporate bodies associated with a resource see (18.4) EXAMPLE Editor, Compiler, Editor of Compilation, Etc.
6JSC/ALA/Discussion/1 Machine-Actionable Data Elements in RDA Follow up to 6JSC/ALA/17 Recommendations 1.Add Extent of Expression to the RDA element set … 2.Add Extent of Item to the RDA element set, to parallel Extent of Manifestation and the proposed Extent of Expression. 3.Extend the RDA/ONIX Framework for Resource Categorization, in order to flesh out fuller sets of types for content and carrier 4.Modify the Aspect-Unit-Quantity (AUQ) model, as presented below, to accommodate complex extent data.
Recommendation 1. Extent of Expression Add Extent of Expression to the RDA element set and consider making it core when the extent is readily ascertainable and considered important for identification or selection. The extent of an expression is a quantification of the intellectual content of the expression (e.g., number of words in a text, statements in a computer program, images in a comic strip, etc.). For works expressed as sound and/or motion the extent may be a measure of duration (e.g., playing time). FRBR Current instructions refer to content (e.g. 1 map) as well as carriers. A new element would enable separation of content and carrier: e.g. 2 sheets, 4 maps
Questions For EURIG: 1.Does EURIG agree to addition of new element Extent of Content? 2.Should it be core, if readily ascertainable and considered important for identification or selection? 3.Should values for Extent of Expression be based upon the RDA vocabulary for Content Type?
Recommendation 2: Extent of Item Add Extent of Item to the RDA element set, to parallel Extent of Manifestation and the proposed Extent of Expression. Question: Should an identical machine- actionable model be established for all three of these extent elements. What would be the use case for extent of item?
Recommendation 3: RDA/ONIX Framework Extend the RDA/ONIX Framework for Resource Categorization, in order to flesh out fuller sets of types for content and carrier. Questions: a. Should the RDA vocabularies for Content Type (RDA 6.9) and Carrier Type (RDA3.3) be extended in order to establish more user-friendly terms for extents of expression and manifestation? b. If so, should a separate group be charged to develop draft category tables, vocabulary values, and label construction patterns for RDA categorization terms?
Recommendation 4: Aspect/Unit Quality/Model AUQ Aspect: extent/number of subunits Unit: pages Quantity: 245 Aspect: height Unit: centimeters Quantity: 23 Current 245 pages ; 23 cm
6JSC/ALA/26 Colour content Recommendations 2Single Vocabulary for colour content of all resources 3Define colour 5Grey scale should be used only for digital resources 6Tinted and Toned: production method or colour content? 7Sepia (retained) 8Order of elements (none) 9Expand to cover non-textual resources 10Hand colouring (restricted to item)
Vocabulary black and white black and white (tinted) black and white (tinted and toned) black and white (toned) colour [or color] sepia grey scale
Glossary Colour Colour content consisting entirely or in part of primary colour, or colour derived from primary colour
6JSC/ALA/26 Colour content Option 1 1.Vocabulary vs. instructions. a.continues to present instructions for recording particular terms under given circumstances Option 2 instructs the cataloguer to record one or more appropriate terms from the following list: and gives a list of terms.
6JSC/ACOC/8 Addition of the Copyright holder relationship Amendments to and Appendix I 1.Add copyright holders to scope of Other person, family or corporate body associated with the manifestation. 2.Add relationship designator for copyright holder: A person, family, or corporate body that holds a legal right to a manifestation under copyright or similar laws.
Changes Alternative: If the issues or parts are sequentially numbered, choose a source of information identifying the highest numbered issue or part available. Indicate whether the lowest or highest numbered issue or part available has been used as the basis for identifying the resource as a whole by a note (see RDA) or some other suitable means. – c) If the resource has unnumbered issues or parts, or if it has numbering that does not
JSC Papers 2: Internationalisation Papers for discussion 6JSC/DNB/Discussion/1: First issue v. latest (current) issue 6JSC/LC/25 Recording dates in more than one calendar 6JSC/DNB/? Parts of the Bible: Books (RDA ) 6JSC/ALA/23/Revision proposal for RDA instructions for treaties DBC proposals for Appendix I Relationship Designators
6JSC/DNB/Discussion/1: First issue v. latest (current) issue FRBR makes no recommendation regarding first issue or last issue as the source of information for description of serials. AACR2, ISSN, RDA require first issue. RAK/ZETA (ZDB) Serials Union Catalogue for Germany & Austria has requirement for latest issue. Only affects minor changes LOTS of legacy data
6JSC/DNB/Discussion/1: First issue v. latest (current) issue Consultation ISSN Review Group, CONSER, EZB, ISBD Review Group, OCLCetc. Proposals 1.Short term: co-exist 2.Identical entities to enable mapping between records 3.Identify first/latest approach explicitly in records
Interim/Low Impact solution Alternative instruction at b) and c) to permit latest issue New instruction at to indicate basis for identification of the resource. Reflect alternatives in related instructions Large number of alternative instructions generated.
Solution New elements Later parallel title/Earlier Parallel Later statement of responsibility/Earlier statement of responsibity Name of later publisher/Name of earlier publisher Chronological element (as per MARC 260/264) Core requirement : current or earliest
6JSC/LC/25 Recording dates in more than one calendar Example of change Date of Publication CORE ELEMENT If the date of publication appears on the source of information in more than one calendar, only the date in the calendar preferred by the agency preparing the description is required add new paragraph If dates appearing on the resource are represented in different calendars, record the dates in the order indicated by the sequence, layout, or typography of the dates on the source of information. Optional Omission If the dates appearing on the resource are represented in different calendars, record only the date in the calendar preferred by the agency preparing the description add An alternative chronological designation may include a date in a different calendar. Summary Scope of change Date of Production Date of Publication Date of Distribution Date of Manufacture Alternative Chronological Designation of First Issue or Part of Sequence. Scope Purpose Encourage representation of the resource Alignment with ISBD Allow dates to be recorded in calendar preferred by the agency
6JSC/DNB/1/ Parts of the Bible: Books (RDA ) Proposed revision , first paragraph: Books For books of the Catholic or Protestant canon, record the brief citation form of the Authorized Version according to common usage in a language and script preferred by the agency creating the data as a subdivision of the preferred title for the Bible. If the preferred language of the agency creating the data is English, use the brief citation form of the Authorized Version. Summary The Authorized (King James) Version of the Bible is accorded undue precedence in RDA. Replace current text with a more neutral instruction. Purpose Convenience of users Internationalisation Question Should the highlighted text be added or omitted?
6JSC/ALA/23/Revision proposal for RDA instructions for treaties Recommendations Record the title of the treaty as the preferred title for all treaties, and use the title of the treaty as the basis for the authorized access point. Create a generic definition of treaty for the Glossary and using that term in the RDA text to signify all kinds of treaties and international agreements. Broaden the definition of RDA (Date of Signing of a Treaty, Etc.) to include the date of adoption, and simplify the punctuation to always use parentheses. Minor changes to examples and other instructions Summary 27 specific proposals Recommendations from US law cataloguers. Preferred title should be under treaty not first named jurisdiction. Dont use conventional collective title Treaties, etc. Justification Convenience of the user Representation of the resource All signatories treated equallly Questions for EURIG Does this meet requirements outside USA? Retrospective impact?.
DBC Proposed Fast Track Relationships Designators (Appendix I) Artist needlework designer An artist responsible for creating a pattern for knitting, a piece of embroidery etc. Author creator of recipe A creator of recipes for cooking Other…Corporate Body Associated with the Work responsible corporate body. A corporate body that can not be considered a creator according to and also isnt mentioned specific as publisher, host institution, issuing body or sponsoring body, but still takes some kind of ownership for the content. Contributor keeper of the minutes (expression) A person, family, or corporate body contributing to an expression of a work by reporting what is said in a meeting, at a lecture etc. Performer reader A type of performer contributing to an expression of a work by reading aloud an audiobook
Activity Plan WhatWhoWhen Discussion Paper on Illustrations for JSC 2013 Aggregates WGFor JSC meeting 2013 Discussion Paper on Compilations for JSC 2013 French Working Group RDA with the Aggregates WG For JSC meeting 2013 Adaptation 6JSC/EURIG/2Françoise Leresche (BnF)To be confirmed after JSC meeting Express EURIG point of view during JSC for 6JSC/EURIG/3 Alan Danskin (BL)November 5-9 Form a group for MusicChristine Frodl (DNB) Response to 6JSC/ALA/17Verena SchaffnerASAP (JSC deadline: October 8 th ) Response to 6JSC/ALA/18Biblioteca Nacional de EspañaASAP (JSC deadline: October 8 th ) Response to 6JSC/ALA/19Christian Aliverti (SNL)ASAP (JSC deadline: October 8 th ) Response to 6JSC/ALA/16Gildas Ilien (BnF) / Alan Danskin (BL)ASAP (JSC deadline: October 8 th ) Proposal additions to RDA Toolkit Appendix I (relationship designators) Hanne Hørl Hansen (DB)December 2012? Response to 6JSC/ALA/11Alan Danskin (BL)ASAP (JSC deadline: October 8 th ) Research topic 6JSC/ALA/14Working Group on MusicBy July 2015? Response to 6JSC/CCC/6Alan Danskin (BL)ASAP (JSC deadline: October 8 th ) Response to 6JSC/LC/12Françoise Leresche (BnF)ASAP (JSC deadline: October 8 th ) Verbal response to 6JSC/LC/13Alan Danskin (BL)JSC Meeting Response to 6JSC/ALA/11Alan Danskin (BL)ASAP (JSC deadline: October 8 th ) Members SurveyKatharine Gryspeerdt (BL)February 2013
Future meetings Members meeting 2014: National Library of Switzerland or Vienna? Additional meeting (Members survey) Yes=5 No=10 Some interest in meetings on specific topics In conjunction with other events
Future meeting hosts Austrian Library Network BNF (2015-) (hosted technical meeting, 2012) DNB (hosted inaugural meeting, 2011) British Library (2015-) Danish Book Center National Library of Norway National Library of Latvia (2016) OCLC/KB Netherlands
Welcome to DAY 2
JSC Papers 3: Subject Papers for discussion 6JSC/ALA/Discussion/2 Treatment of Subjects in RDA 6JSC/Chair/8 Proposals for Subject Relationships
Background RDA does not cover subject – FRSAD model not available in time Placeholder chapters only – FRBR Group 3 entities – Chapter 16 places incomplete Discussed in Glasgow in 2011 Light touch; FRBR entities; subject relationship Chair/8 is a follow up to that discussion
FRBR GROUP 3 – Concept – Object – Event – Place – Group 1 – Group 2
FRSAD: the conceptual model of aboutness Thema = anything that can be the subject of a Work…Thema is independent of language and disciplines Nomen = any alphanumeric, sound, visual, or any other symbol, sign, of combination of symbols, by which a Thema is known, referred to, or addressed. Work Thema Nomen has subject / is subject of has appellation / is appellation of
RDA Choices 6JSC/Chair/8 Add FRSAD Model at – RDA follows, spirit of FRSAD model – Subject relationship work has subject/is subject of can be applied to any entity. Define Concept, Object, Event as entities. Expand Placeholder chapters expanded 6JSC/ALA/Discussion/2 Adopt FRSAD Model – Thema / Nomen – Subject relationship has subject / is subject of – Rename Thema / Nomen as Subject / Name of Subject – Make Name of Subject an attribute of Subject Replace placeholder chapters with general subject chapters. – Move instructions for jurisdictions & other corporate bodies from Chapter 16 to Chapter 11