Successfully reported this slideshow.
Your SlideShare is downloading. ×

NARDAC RDA Update Forum 8.3.20

Ad

1
August 3, 2020NARDAC RDA Update Forum
North American RDA Committee
RDA Update FORUM
Monday, August 3, 2020

Ad

2
August 3, 2020NARDAC RDA Update Forum
What is NARDAC?
•North American RDA Committee
• Represents the North American regi...

Ad

3
August 3, 2020NARDAC RDA Update Forum
NARDAC Communities
• United States
 American Library Association (ALA)
 Library ...

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Check these out next

1 of 95 Ad
1 of 95 Ad
Advertisement

More Related Content

Similar to NARDAC RDA Update Forum 8.3.20

Advertisement

NARDAC RDA Update Forum 8.3.20

  1. 1. 1 August 3, 2020NARDAC RDA Update Forum North American RDA Committee RDA Update FORUM Monday, August 3, 2020
  2. 2. 2 August 3, 2020NARDAC RDA Update Forum What is NARDAC? •North American RDA Committee • Represents the North American region on the RDA Steering Committee (RSC) • Formed in January 2018
  3. 3. 3 August 3, 2020NARDAC RDA Update Forum NARDAC Communities • United States  American Library Association (ALA)  Library of Congress (LC) • Canada  Canadian Committee on Cataloguing (CCC) [Bermuda, Greenland, Saint Pierre and Miquelon: If/when they implement RDA]
  4. 4. 4 August 3, 2020NARDAC RDA Update Forum Current members of NARDAC American Library Association (ALA) Representatives • Dominique Bourassa, Yale University, NARDAC Chair • Stephen Hearn, University of Minnesota, Back-up Representative to the RSC Canadian Committee on Cataloguing (CCC) Representatives • Thomas Brenndorfer, Guelph Public Library, NARDAC Representative to the RSC • Thi Bao Tran Phan, Library and Archives Canada Library of Congress (LC) Representatives • Damian Iseminger, Bibliographic Access Section, Music Division, NARDAC coordinator of Web Content • Melanie Polutta, Policy, Training, and Cooperative Programs Division RDA Board National Institution Representative from North America (ex officio) • Merideth Fletcher, LAC
  5. 5. 5 August 3, 2020NARDAC RDA Update Forum NARDAC Charge • Formulate North American positions on RDA proposals, discussion papers, and drafts • Keep the North American communities informed of RDA developments and RSC decisions • Select a member of NARDAC to serve as the North American regional representative to the RSC • Respond to other RSC initiatives as they arise • Support the work of RSC by helping to identify possible members for the working groups Source: NARDAC Terms of Reference http://www.rda- rsc.org/sites/all/files/North%20American%20RDA%20Committee_TermsOfReference2017.pdf
  6. 6. 6 August 3, 2020NARDAC RDA Update Forum NARDAC Goals • Develop effective interaction with the communities NARDAC represents • Become a support and information hub • Provide direction to constituent groups that assume training responsibilities • Extend outreach
  7. 7. 7 August 3, 2020NARDAC RDA Update Forum NARDAC Challenges • only 6 members representing a widespread region • for operations https://commons.wikimedia.org/wiki/File:Northern_America_(orthographic_projection).svg
  8. 8. 8 August 3, 2020NARDAC RDA Update Forum Switch over date for the beta RDA Toolkit 15 December
  9. 9. 9 August 3, 2020NARDAC RDA Update Forum Presentations • Recordings: https://www.youtube.com/c/RDAToolkitVideo • Slides: http://www.rda- rsc.org/northamerica/presentations/
  10. 10. 10 August 3, 2020NARDAC RDA Update Forum RDA – Hot topics Thomas Brenndorfer RDA Forum – August 3, 2020
  11. 11. RDA Steering Committee meetings 2020 11 August 3, 2020NARDAC RDA Update Forum • January 6-9, 2020 • April 6-9, 2020 • July 6-9, 2020 • planned – weeks of October 12 and October 19, 2020
  12. 12. RDA Steering Committee meetings 2020 12 August 3, 2020NARDAC RDA Update Forum • January 6-9, 2020 String encoding schemes (chiefly for constructing access points) - moved to policy statements; allow for scalability Content elements for aggregates - supplementary, accessibility, illustrative, colour, sound as manifestation shortcut elements Implementation scenarios updated - A – Linked open data; B – Relational or object-oriented data; C – Bibliographic/authority data; D – Flat file data
  13. 13. RDA Steering Committee meetings 2020 13 August 3, 2020NARDAC RDA Update Forum • April 6-9, 2020 Display labels for RDA elements - progress report on NARDAC “friendly labels” project Community vocabularies - update on resources menu (former appendixes); eliminating Western focus; SES (string encoding scheme) project Representative expression elements for aggregating works - completion of content elements and aggregates issues
  14. 14. RDA Steering Committee meetings 2020 14 August 3, 2020NARDAC RDA Update Forum • July 6-9, 2020 RDA Entity boundaries - i.e., when to make new descriptions for entities Toolkit menu for Resources tab - rearranging this menu for final release of Toolkit RDA conformance and “well-formed data” - RDA metadata statements (subject-predicate- object) are the building blocks for interoperability
  15. 15. Representative expression elements and their use for aggregating works 15 August 3, 2020NARDAC RDA Update Forum
  16. 16. Representative expression elements for a work 16 August 3, 2020NARDAC RDA Update Forum Work Content Type Date of Expression Language of Expression Medium of Performance of Musical Content Duration Intended Audience of Expression Expression Expression Expression Expression
  17. 17. 17 August 3, 2020NARDAC RDA Update Forum Work Content Type = text Language of Expression = English Expression Expression Expression Expression Language of Representative Expression = English Content Type of Representative Expression = text Representative expression elements for a work
  18. 18. Representative expression 18 August 3, 2020NARDAC RDA Update Forum Work Expression Expression Expression Expression Representative Expression
  19. 19. Representative expression elements for an aggregating work 19 August 3, 2020NARDAC RDA Update Forum Aggregating Work Aggregating Expression Expression Expression Expression Expression Expression Expression aggregates
  20. 20. 20 August 3, 2020NARDAC RDA Update Forum Aggregating Work Aggregating Expression Language of Expression = English Language of Expression = French Content Type = text Language of Representative Expression = English Language of Representative Expression = French Content Type of Representative Expression = text Representative expression elements for an aggregating work
  21. 21. Example: Different albums of the same songs could have different cumulative values for duration: - different aggregating works because of differences in expressions aggregated - but can be collocated under an Authorized access point for work group 21 August 3, 2020NARDAC RDA Update Forum Aggregating Work Aggregating Expression Cumulation of values of Duration Duration of Representative Expression Representative expression elements for an aggregating work
  22. 22. Toolkit menu tab for Resources 22 August 3, 2020NARDAC RDA Update Forum
  23. 23. 23 August 3, 2020NARDAC RDA Update Forum
  24. 24. Resources menu 24 August 3, 2020NARDAC RDA Update Forum Resources •Glossary •Vocabulary encoding schemes •Community resources •Revision history •AACR2 Capitalization of transcriptions to be reviewed for Guidelines on normalized transcription. Community Resources Abbreviations Abbreviations for countries and states Abbreviations in Cyrillic script Abbreviations in Greek script Abbreviations in Hebrew script Abbreviations in Latin script Books of the Bible Books of the Bible: Library of Congress- Program for Cooperative Cataloging Festlegungen für den deutschen Sprachraum zum Erfassen der bevorzugten Titel von biblischen Schriften Livres de la Bible : Bibliothèque et Archives Canada-Bibliothèque et Archives nationales du Québec Terms for collective titles Terms for gender Terms for medium of performance Terms in specific languages [toc for 64 languages from Afrikaans to Yiddish] Terms of rank Additional instructions for names of persons and initial articles to be reviewed as part of String Encoding Scheme project.
  25. 25. Thank you! 25 August 3, 2020NARDAC RDA Update Forum
  26. 26. RDA/PS conversion project update: the LC/PCC policy statements Melanie Polutta LC representative to NARDAC August 3, 2020NARDAC RDA Update Forum26
  27. 27. What is the project? Changing our documentation to work with the beta RDA Toolkit that will go live in December 2020 (RDA Toolkit) August 3, 2020NARDAC RDA Update Forum27
  28. 28. Background information • Documentation to be created:  Policy statements  Application profile  metadata guidance documentation • Date of implementation TBD for RDA Toolkit released on December 15, 2020 • PCC Policy Committee (PoCo) agreed to project plan, with monthly status reports and issues requiring discussion August 3, 2020NARDAC RDA Update Forum28
  29. 29. Changes • Organization of beta RDA Toolkit is radically different  By high-level entity  Modular • Fundamental changes in four areas of Diachronic Works, Element Labels, Data Provenance, Aggregates August 3, 2020NARDAC RDA Update Forum29
  30. 30. Addressing the changes • Joint LC/PCC Task Groups  Diachronic Works  Element Labels  Data Provenance  Aggregates August 3, 2020NARDAC RDA Update Forum30
  31. 31. Who is working on it? Policy, Training, and Cooperative Programs Division leads the effort, with assistance from LC catalogers and PCC PoCo August 3, 2020NARDAC RDA Update Forum 31
  32. 32. Who is working on it in LC? • Project manager: Judith Cannan, Chief of PTCP • Assignment manager: Clara Liao, Section Head of PTCP/CTPS • Project lead: Melanie Polutta (PTCP/CTPS) • Project management resource: Ivey Glendon (PTCP/CPPS) • PTCP members: Paul Frank, Manon Théroux, Veronica Ranieri, Les Hawkins (retired), Ivey Glendon • SCD/MD: Damian Iseminger • ABA: Jacque Brellenthin, Sarah Byun, Steven Folsom, Bill Robboy, Trina Soderquist, Jessica Zieman • Outside ABA: special format catalogers that we will bring in for consultation August 3, 2020NARDAC RDA Update Forum32
  33. 33. Parts of the project • 6 phases, overlapping in time  Phase 1: Analyze policy statements  Phase 2: DITA markup conversion of PSs  Phase 3: Application profile  Phase 4: Testing of policy statements  Phase 5: Metadata guidance documents  Phase 6: Training • Implementation! August 3, 2020NARDAC RDA Update Forum33
  34. 34. Phase 1 • Analyze policy statements: Phase 1a  Cataloger analyzes current policy statements and writes new ones  Proofreader reviews what first cataloger wrote  Original writer finalizes their policy statements • Analyze policy statements: Phase 1b  Cataloger analyzes the full RDA text to write new policy statements  Cataloger brings 1a text into cohesion with 1b text August 3, 2020NARDAC RDA Update Forum34
  35. 35. Phase 2 & 3 • DITA team created:  Ivey Glendon, Daniel Griffin, Damian Iseminger, Clara Liao, Melanie Polutta, Manon Théroux  Currently studying DITA as a group  Batch of test policy statements created for April 29th update  Working out best practices so we are ready when Phase 1 is done • Application profile  A format for AP spreadsheet has been established  Working out a methodology for how to handle it • Phases 4, 5, & 6 not yet started August 3, 2020NARDAC RDA Update Forum35
  36. 36. Challenges! • Complexity of the work • Growth of the project  String Encoding Scheme (SES) decision by RSC to hand these to community control • Pandemic impact August 3, 2020NARDAC RDA Update Forum36
  37. 37. Challenging, maddening, exciting, exhausting, interesting work… Thank you for your attention If you would like to see more detail about this work, see this link for a presentation: http://login.icohere.com/PCC?pnum=PGZ70039 August 3, 2020NARDAC RDA Update Forum37
  38. 38. 38 Getting ready for the new RDA Toolkit : updates from Library and Archives Canada Thi Bao Tran Phan, CCC representative on NARDAC August 3, 2020NARDAC RDA Update Forum
  39. 39. 39 LAC’s context • Bilingual national institution ▪ Policy on bilingualism • Bibliographic and authority records created in French, English, or both August 3, 2020NARDAC RDA Update Forum
  40. 40. 40 Recent innovations at LAC • LAC’s catalogue in OCLC’s WorldShare Management Services (WMS) • LAC is a member of NACO • Canadiana Name Authorities in French (Canadiana in WMS) ▪ PFAN authorities file August 3, 2020NARDAC RDA Update Forum
  41. 41. 41 Francophone Name Authority Programme (PFAN) • Collaboration between LAC, Bibliothèque et Archives nationales du Québec (BAnQ) and fifteen university libraries from the Bureau de coopération interuniversitaire (BCI) • Based on the NACO model for its gouvernance structure, programme and policies • Officially launched on June 2020 August 3, 2020NARDAC RDA Update Forum
  42. 42. 42 Cataloguing at LAC • Bibliographic records in WMS • 2 files for authorities ▪ LC/NACO ▪ Canadiana/PFAN • 3 files for subject headings ▪ Library of Congress Subject Headings (LCSH) ▪ Canadian Subject Headings (CSH) (accessible in WMS via Canadiana) ▪ Répertoire de vedettes-matières (RVM) (accessible in WMS) August 3, 2020NARDAC RDA Update Forum
  43. 43. 43 Current policy statements • Bilingual • Library system: Amicus • LAC-BAC/BAnQ statements ▪ LAC practice: available in English and French RDA ▪ BAnQ practice: available in French RDA only August 3, 2020NARDAC RDA Update Forum
  44. 44. 44 New policy statements • Bilingual • Specific to Canada and to LAC, while still closely aligned with LC • Aligned with PCC • Aligned with PFAN • New library system: WMS • Collaboration with BAnQ for the creation of policy statements in French in the RDA Toolkit August 3, 2020NARDAC RDA Update Forum
  45. 45. 45 August 3, 2020NARDAC RDA Update Forum O Actions before the implementation of the policy statements in the new RDA Toolkit Planning of the work and the implementation date. Analysis of the current policy statements in relation to the new RDA Toolkit. Communicating to the Canadian library community via CCC. Writing and revision of the English texts of statements specific to Canada and to LAC, based on policy statements by LC and PCC (NACO). Translation of the statements to French. Writing of the French texts of policy statements by the PFAN. Translation of the statements to English. Creating the statements in the RDA Toolkit. Collaborating with BAnQ for the French statements.
  46. 46. 46 Application profiles • Analysis of staff’s needs • Elizabeth Sanders, acting manager of Description is a member of the Application Profiles Working Group August 3, 2020NARDAC RDA Update Forum
  47. 47. 47 Implementation • The implementation date of the policy statements is influenced by ▪ Other priorities for 2020-2021 o PFAN ▪ French translation of the RDA Toolkit ▪ LC/PCC policy statements • LAC will communicate its implementation schedule in the fall August 3, 2020NARDAC RDA Update Forum
  48. 48. 48 Questions? August 3, 2020NARDAC RDA Update Forum
  49. 49. Translating the new RDA Toolkit into French North American RDA Committee Update Forum August 3, 2020 Daniel Paradis Translations Team Liaison Officer Bibliographic Standards Librarian Bibliothèque et Archives nationales du Québec
  50. 50. 2010 : the beginnings •Word file for •each chapter (including examples) •each appendix •glossary • Word file of recurring phrases August 3, 202050 NARDAC RDA Update Forum
  51. 51. 3R Project • Translation and registry synchronization process implemented in 2017 • December 2017 release: Glossary and Appendices I, J, K and M in French translation were produced using RDA Registry data • Preliminary step: translating RDA Reference using templates in CSV format August 3, 2020NARDAC RDA Update Forum51
  52. 52. 3R Project • Data from the Registry will be used to populate • Parts of entity and element pages • Name of entity/element • Definition and Scope • Element Reference box • List of controlled terms • Glossary • Vocabulary encoding schemes August 3, 2020NARDAC RDA Update Forum52
  53. 53. 3R Project • And parts of examples August 3, 2020NARDAC RDA Update Forum53
  54. 54. 3R Project •SDL Trados Studio (computer-assisted translation tool) •Includes tools to facilitate the translation process • translation memory • terminological databases August 3, 2020NARDAC RDA Update Forum54
  55. 55. Outline of an element chapter [name of element] Definition and Scope Element Reference IRI Domain Range Alternate labels Dublin Core Terms MARC 21 [Authority and/or Bibliographic] Prerecording Recording Recording an unstructured description Recording a structured description Recording an identifier Recording an IRI Related elements August 3, 2020NARDAC RDA Update Forum55 Translation table
  56. 56. DITA model and boilerplate file • DITA data model implemented in 2017 • Boilerplate file is an example of how the DITA model improved content management and the translation process • Contains sentences and paragraphs that are frequently re-used in the RDA text • Improved, more granular version of recurring phrases document • When needed in a specific instruction, boilerplate text is pulled into RDA instructions using content references or content key references • Boilerplate text needs to be translated and, if needed, revised only once August 3, 2020NARDAC RDA Update Forum56
  57. 57. Boilerplate file August 3, 2020NARDAC RDA Update Forum57
  58. 58. Boilerplate file • RDA has 3,017 elements (as of May 26) • Instructions for 2,536 elements (84%) are composed entirely of boilerplate and will be translated automatically • Ex. “printer agent of” • Only instructions for 481 elements (16%) will have to be translated by a translator August 3, 202058 NARDAC RDA Update Forum
  59. 59. Issues encountered during translation • Using parentheses to qualify similar labels by element range was found inconsistent and confusing in the English version; parentheses were removed • augmentation of (work)  augmentation of work • catalogue (work)  catalogue work • Parentheses cannot always be easily removed in French • augmentation of work  augmentation d’une œuvre • sequel work  œuvre …? • catalogue work  œuvre catalographique? • Parentheses retained in some instances • suite (œuvre) • catalogue (œuvre) August 3, 2020NARDAC RDA Update Forum59
  60. 60. Issues encountered during translation • Typos • Inconsistencies between similar definitions • Ambiguities in wording • Problematic definitions. For example : • Definitions not adjusted for elements that had become relationship elements. Example: • coordinates of cartographic content (range = Place) • Original definition in beta Toolkit: A mathematical system for identifying a place covered by the cartographic content of a work. • Revised definition: A place that is the area of coverage of a cartographic work that is described using a mathematical system to identify its boundaries or location. August 3, 2020NARDAC RDA Update Forum 6 0
  61. 61. Problem with “issue” • Does issuing cover only publication? What is the distinction between publication, release and issuance? • Scope note for name of publisher: Publication includes release and issuance. Google translation of note (July 2019): La publication inclut la publication et la publication (!!). • issuing body agent, issuing body collective agent, issuing body corporate body, etc. • Issuing body used to refer only to a corporate body under AACR2. How to translate issuing body when the term applies to all types of agents? Could body be omitted? August 3, 2020NARDAC RDA Update Forum61
  62. 62. Next steps RDA Reference • Value vocabularies • Element sets Translation Table Boilerplate file Toolkit instructions • Entity chapters • Guidance chapters • Related resources User interface Examples Help August 3, 2020NARDAC RDA Update Forum62 Expected date of completion : May 31, 2021
  63. 63. To learn more about the original French translation project: Clément Arsenault, Daniel Paradis & Pat Riva (2014) Translating RDA into French, Cataloging & Classification Quarterly, 52:6-7, 704-722, DOI: 10.1080/01639374.2014.889059 August 3, 2020NARDAC RDA Update Forum63
  64. 64. August 3, 202064 Questions? NARDAC RDA Update Forum
  65. 65. RDA Toolkit Update James Hennelly Director, RDA Toolkit jhennelly@ala.org August 3, 2020 August 3, 202065
  66. 66. 66 Next Release to Beta Site August 3, 2020 • Scheduled for September 16th • Will include… ▪ Partial translations in Finnish and Norwegian ▪ Functionality for setting language preference and switching between language versions ▪ Improvements to contributed documents, particularly the subscribe functions ▪ Additional policy statements from LC-PCC and British Library ▪ Restructuring of the Resources tab • Final Beta Release
  67. 67. 67 December Switchover • Will focus on the switchover with minimal development or editorial work • Beta site will become access.rdatoolkit.org • Beta.rdatoolkit.org will go away • Original RDA Toolkit will move to new address and remain accessible to all • Aiming to not to break any links and preserve profile-related content (setting, bookmarks etc.) August 3, 2020
  68. 68. 68 Feedback James Hennelly jhennelly@ala.org rdatoolkit@ala.org We still want it. August 3, 2020
  69. 69. 69 August 3, 2020NARDAC RDA Update Forum RDA Conformance in a Complex Environment Stephen Hearn (University of Minnesota) ALA representative to NARDAC
  70. 70. RDA Conformance 70 August 3, 2020NARDAC RDA Update Forum • RSC discussion paper, May 2020 • Discusses degrees of metadata conformance with RDA • Proposed replacement for “Data Elements” Guidance chapter • http://www.rda-rsc.org/sites/all/files/ RDA%20conformance%20proposal.pdf
  71. 71. Indirect and partial conformance 71 August 3, 2020NARDAC RDA Update Forum • Indirect conformance = conformance with RDA entities or elements at a narrower level • Partial conformance = RDA description set + non-RDA metadata in one package • Unconstrained element set in RDA Registry = non-RDA metadata for use outside of RDA
  72. 72. Complex environment 72 August 3, 2020NARDAC RDA Update Forum • Cataloging works with three systems  Content standard (e.g., AACR2, RDA)  Encoding format (e.g., MARC, RDF)  Automated system (e.g., OCLC, Alma) • Not fully congruent or compatible • Indirect and partial conformance with RDA will be widely practiced
  73. 73. Closed vs Open World 73 August 3, 2020NARDAC RDA Update Forum • Do RDA entity classes and element constraints result in a closed world? • Linked data prefers identifiers • RDA requires RDA entities, but not RDA entity descriptions • RDA recognizes the potential for equivalent or compatible element semantics • RDA accepts partial conformance
  74. 74. Catalogers make it all work 74 August 3, 2020NARDAC RDA Update Forum • Cataloging is a practical activity • Catalogers work to ensure that:  Metadata responds to user needs  Metadata can be communicated and shared  The strengths of standards, formats, and systems can be leveraged together • RDA conformance is advantageous, but it’s not the only semantic game we play
  75. 75. Questions? 75 August 3, 2020NARDAC RDA Update Forum
  76. 76. 76 3R is Almost Done – What’s Next? August 3, 2020NARDAC RDA Update Forum Kathy Glennan Chair, RDA Steering Committee Head, Original & Special Collections Cataloging University of Maryland Libraries
  77. 77. 77 3R Project – Final Milestones • September RDA Toolkit release  More policy statement examples from LC and the British Library  Partial translations published in Finnish and Norwegian  Mapping of RDA elements to LRM elements • Switchover date: December 15, 2020  Beta Toolkit ceases being beta and becomes the authorized version of RDA o New URL: access.rdatoolkit.org  Original Toolkit still available o New URL: original.rdatoolkit.org o No date set yet for retiring the original Toolkit • You will have at least a one-year notification August 3, 2020NARDAC RDA Update Forum
  78. 78. 78 Timeframe for Implementation August 3, 2020NARDAC RDA Update Forum
  79. 79. 79 Timeframe for Implementation • Up to communities, based on  Availability of their own application profiles, policy statements, best practices, etc.  Completion of local training initiatives  Possibly: implementation of additional RDA-related content designation in MARC 21, BIBFRAME, or other encoding standard • There may be a coordinated implementation date among some national libraries world-wide  This happened with the original RDA August 3, 2020NARDAC RDA Update Forum
  80. 80. 80 A Few Things to Remember • RDA was never designed to meet all your metadata needs  Administrative metadata, resource management metadata, and rights management metadata are all out of scope of RDA o As is subject access, unless it’s for an RDA entity  RDA can point out to other standards with related entity of RDA entity or something more specific (e.g., related entity of [agent, place, work, etc.]) as attributes of an RDA entity • “Core elements” not part of beta RDA  Required elements are quite minimal at the RDA (or international) level  More specific guidance/requirements expected in application profiles, policy statements, and/or best practices August 3, 2020NARDAC RDA Update Forum
  81. 81. 81 A Few Things to Remember Just because an element is defined in RDA does not mean catalogers have to use it August 3, 2020NARDAC RDA Update Forum
  82. 82. 82 What does RDA Require? • Coherent description of an information resource  [Required] A description of at least one of its entities  [Recommended] Relationships between WEMI entities for the information resource, using specific relationship elements with the appropriate cardinality, such as the following (full list at 07.04.34.92): o expression manifested [minimum = 1; maximum not specified] o manifestation of work [minimum number = 1; maximum not specified] • This relationship implies the existence of at least one expression • Description of a WEMI entity  [Required] An appellation element (appellation, title/preferred title, access point/authorized access point, identifier, or IRI)  [Recommended] Other elements to support LRM user tasks August 3, 2020NARDAC RDA Update Forum
  83. 83. 83 What Will Communities Require? • Cataloging communities will determine for themselves  Choices in granularity (e.g., agent vs. a more specific entity like person)  Recording method(s) for a given element o unstructured, structured, identifier, IRI  Which additional elements are required, and which of these are repeatable (beyond what is already in RDA)  Which elements will not be used August 3, 2020NARDAC RDA Update Forum
  84. 84. 84 What’s Next for the RSC? • October 2020 meeting changed from in-person to virtual  Expanded from one week to two weeks  Will be a mix of synchronous and asynchronous meeting styles o Will hold 4 two-hour synchronous meetings at different times to accommodate the different time zones of RSC members o Investigating how to accommodate observers o Agenda items may cross over between both meeting styles  Papers, reports, etc. to be posted on the RSC website no later than three weeks before the meeting • 4 meetings planned for 2021  3 asynchronous (January, April, July)  1 in person – in New Zealand August 3, 2020NARDAC RDA Update Forum
  85. 85. 85 RDA Development Goals 2020-2021 • Continued collaboration with MARC/RDA Working Group  More proposals and discussion papers related to new RDA elements expected for MARC Advisory Committee meeting in January 2021 • Receive and act on initial recommendations from RSC’s Application Profiles Working Group • Consider proposals from RDA communities as they arise  Currently under development by NARDAC o curator agent of work/curator agent of work of • Support for new RSC member to represent Latin America and the Caribbean (anticipated no later than 2021) August 3, 2020NARDAC RDA Update Forum
  86. 86. 86 RDA Development Goals 2020-2021 • Ongoing review and update of RDA to reduce, and ultimately eliminate, Western focus  Current work on developing community-based string encoding schemes is part of this effort • Continued development of and support for “community resources” in the Toolkit  Including identifying what constitutes a “community” and what their relationship is with the RSC • Create a self-service checklist of conformance conditions • Respond to user feedback August 3, 2020NARDAC RDA Update Forum
  87. 87. 87 More Information – all free! • RSC website: http://rda-rsc.org/  RSC news and announcements: http://rda-rsc.org/news  RSC documents (2020): http://rda-rsc.org/node/633 (RSC papers, agendas, minutes, working group charges, etc.)  RSC presentations (2020): http://www.rda-rsc.org/node/634 • RDA Toolkit site: https://www.rdatoolkit.org/  Toolkit news: https://www.rdatoolkit.org/news • RDA Toolkit YouTube channel  https://www.youtube.com/c/RDAToolkitVideo (contains instructional videos on how to use the RDA Toolkit and recordings of RDA-related presentations) • Email me: RSCChair@rdatoolkit.org August 3, 2020NARDAC RDA Update Forum
  88. 88. 88 Questions?? August 3, 2020NARDAC RDA Update Forum
  89. 89. 89 August 3, 2020NARDAC RDA Update Forum https://www.clipart.email/download/6298794.html
  90. 90. 90 August 3, 2020NARDAC RDA Update Forum Remember https://www.pngegg.com/en/png-ztupu There are still pieces that need to fall into place before we can use the beta RDA Toolkit to catalog.
  91. 91. 91 August 3, 2020NARDAC RDA Update Forum Switch over date 15 December North American Implementation date(s) ? ? Remember
  92. 92. 92 August 3, 2020NARDAC RDA Update Forum What you can do to prepare for Implementation Day • Look at the free resources listed in Kathy’s presentation • “Play” with the beta Toolkit • Stay tuned for announcements from the RSC, LAC, LC, and other North American RDA specialized communities • Be on the lookout for training opportunities; volunteer in training initiatives • Be open-minded…
  93. 93. 93 August 3, 2020NARDAC RDA Update Forum KEEP CALM AND CATALOGUE ON What you can do to prepare for Implementation Day
  94. 94. 94 August 3, 2020NARDAC RDA Update Forum Thanks ALA Publishing eLearning Solutions • Colton Ursiny • Hannah Murphy • Dan Freeman Presenters: • Thomas Brenndorfer • Melanie Polutta • Thi Bao Tran Phan • Daniel Paradis • James Hennelly • Stephen Hearn • Kathy Glennan
  95. 95. Dominique Bourassa nardacchair@rdatoolkit.org 95 August 3, 2020NARDAC RDA Update Forum CONTACT

Editor's Notes

  • Record value for one or more of the expressions aggregated. Record value that is common to all expressions aggregated.
  •  RDA/PS conversion project update: the LC/PCC policy statements
  • PTCP is not only changing LC’s documentation but also the documentation that is used by the members institutions of the Program for Cooperative Cataloging (PCC).
  • PTCP first task is to review existing policy statements and create new ones. ALA Publishing asked LC to undertake this task. The Beta Toolkit will be launched on December 15, 2020 but no date for its implementation has been fixed. LC will be consulting with PCC to decide on an implementation date. Although LC is charged with this task by ALA, it is a joint LC/PCC project and LC agreed to keep PCC informed throughout the process. LC provides PCC PoCo with monthly reports and separately with issues that LC and PCC need to discuss.
  • The changes in these area are so significant that LC and PCC agreed to set up 4 task groups with co-chairs, one from LC and one from PCC, to examine the changes and make recommendations.
  • PTCP is leading the effort but could not do it without assistance from LC catalogers and PCC.
  • We hope to test it before the implementation dating drawing on PCC and LC catalogers for the test. Why a test? To make sure the work of the Policy Statement and metadata documentation are correctly aligned when creating metadata for an item.
  • One of the first things we realized once we really grappled with the project is that there were actually six phases to it, named here. Each phase is a fairly large project all bit itself!
  • The first phase is what we are inside now. We are close to finishing the 1a stage of Phase 1, which is foundational to all the rest. In this stage, we are carefully analyzing the current policy statements, looking at the reorganized beta Toolkit to figure out where stuff now needs to go – which is sometimes in more than one place – and reword the instructions to match the current RDA content. Because this is so monumental, we have set up a process where one cataloger writes something, another cataloger proofreads it and makes comments, and the returns it to the original writer for modification if needed. We have had plenty of interesting discussions as we navigate this change.
    The next stage of Phase 1, which we are soon to start, we are going to be analyzing the full text of RDA options in order to write new policy statements that didn’t need to exist before, and bring the 1a re-written statements into cohesion with the new text, so that it all works together.
  • Phase 2 is the technical part, in which we take the text we’ve created and then input it into the content management system in the DITA XML standard for the text. The technical group is currently studying DITA together and trying to work out the best practices for how we are going to use it in cooperation with the existing guidelines for the RDA content.
    Phase 3 is for the application profile, which overlaps with the policy statements. We worked out a format for the AP, and how we plan to approach it, but have not yet been able to focus on it.
    Phases 4, 5, and 6 have not yet started, because all of them are depending on the previous three phases.
  • As we have gotten our teeth really into the project, we have found there are some real challenges in getting this work done. One of these is the sheer complexity of the work, in each subproject. Phase 1 is really taking us a while, but I would also note that it is foundation to all the rest.
    Also, the project has grown in unexpected ways.
    And of course, the impact of the pandemic is real. In truth, I have been incredibly pleased with how well our group has continued to produce once we adjusted to the challenges of all telework. I am truly grateful for all the hard work that my colleagues in PTCP and in ABA have persisted in their hard work on this project despite the many distractions and challenges we currently face.

    I am now handing this off to Clara Liao, who came in as a section head to our division in April, and has joined in the work on the project.
  • First, a reminder of the context in which we work:
    Library and Archives Canada is a bilingual national institution, with French and English as the official languages. Our bibliographic description work must therefore reflect that mandate.
    We create bibliographic and authority records in French for publications in French, English records for publications in English, and records in both languages for bilingual publications.
  • Over that past few years, LAC has seen some major changes in the way we work.

    LAC recently moved its library system from in-house Amicus to OCLC's WorldShare Management Services (WMS). This change provided the opportunity for LAC to transition to the Name Authority Cooperative Program (NACO) to manage its English language authority records. A new module, known as "Canadiana Name Authorities in French", has been developed within WMS to house the French-language authorities.
  • The Francophone Name Authority Programme, also known as PFAN (Programme francophone des autorités de noms in French), is a new collaborative programme in which some libraries contribute directly and collectively to the Canadiana file. The programme is the result of collaborative efforts between LAC, Bibliothèque et Archives nationales du Québec, and 15 French-speaking university libraries in Québec. The programme uses the NACO model as the basis for its gouvernance structure, its programme, and its policies and was officially launched in June. Its standards committee is currently working to develop a set of documents to support the work of the PFAN members.
  • To recap, since LAC’s transition to OCLC’s WorldShare Management Services, cataloguers are working with two files for authorities (LC/NACO and Canadiana/PFAN) as well as three files for subject headings (Library of Congress Subject Headings, Canadian Subject Headings, Répertoire de vedettes-matières).

    This large inventory of files will have an impact on the scope of instructions that LAC will have to establish.
  • Right now, LAC’s policy statements in the current RDA Toolkit need to be revised.
    They are available in the Toolkit in both French and English. However, they make reference to the old library system, Amicus, and do not reflect the current environment.
    It is expected that the current structure will be more or less conserved: LAC practice and BAnQ practice.
  • For the policy statements for the new RDA Toolkit, we must follow a few principles. First, the policy statements must be available in both French and English. They must be aligned with LC, PCC, and the PFAN, all while being specific to Canada and LAC where needed. Finally, they must take into account the new work environment that is OCLC WMS as well as our collaboration with BAnQ.
  • This is a preliminary list of actions that must be undertaken to develop LAC policy statements in the new RDA Toolkit. Note that this list is not exhaustive.
  • A side note on application profiles:
    LAC has started work to analyze the work environment and to get a vision of the cataloguing tools that will be used by description staff.
    Furthermore, Elizabeth Sander, acting manager of Description, is a member of the Application Profiles Working Group.
  • In conclusion, given the other priorities that we have for 2020-2021 (such as PFAN), the schedule of the French translation of the RDA Toolkit, and LAC’s need to align with policy statements to be produced by LC/PCC, Library and Archives Canada will not be implementing the new RDA Toolkit on December 15. LAC will determine its implementation schedule in the fall and will communicate this information.
  • Thank you. Are there any questions?
  • In this presentation, I will give an overview of how the 3R Project helped make the translation process more efficient. I will also address some of the issues that we encountered when working on the French translation of the new Toolkit.
  • When we began working on the French translation of RDA back in 2010, we started with simple tools, that is, Word files for the chapters, the appendices and the glossary. We were also provided with a Word file of recurring phrases that we translated at the beginning of the process, to ensure consistency between translators.

    This meant that there was originally a lot of redundant content between instructions and between the definitions and scope notes of elements in the instructions and in the glossary. The process required sustained attention from translators and careful review of their work to achieve consistency.
  • Several steps have been taken over the years to automate the production of RDA Toolkit's content, including the translations.
    One of the objectives of the 3R Project was to implement a process to synchronize RDA translations with RDA Reference data in the RDA Registry so that labels, definitions and scope notes for elements and vocabularies, which appear in instructions, the Glossary and the appendices, could be automatically pulled from the Registry.
    The synchronization process was first used in the English version in 2016 and was implemented for translations in 2017 in the current Toolkit.
    For translation teams, this involved providing translations of RDA Reference using templates in CSV format that were later uploaded to the Registry.
    The slide shows an example of template, in this case the one for the Extension plan vocabulary.

  • The use of Registry data was further expanded in the new Toolkit. It is currently used to populate parts of entity and element pages, the glossary and vocabulary encoding schemes. The same will happen with the translations. For translation teams, this involves updating their translation of RDA Reference since the English version was extensively revised and expanded, in part to support the LRM. This is a significant project that a few teams have completed but that others, including the French team, are still working on.

  • Registry data is also used in parts of examples. The slide shows a view in context example where the element names in the left column and the term “spoken word” in the right column were pulled from the Registry. This means that translators will not have to translate these terms again when working on the examples.

    It is also interesting to note that examples are now grouped in separate files, which should give translators more flexibility if they want to replace or delete existing ones, or add new ones.
  • During the 3R Project, translators also began working with SDL Trados Studio, which is a computer-assisted translation tool. It includes tools such as a translation memory and terminological databases to speed up the translation process and increase its quality. We are now also using SDL Trados GroupShare which is a cloud-based product that allows teams to share translation memories and terminological databases among themselves.
  • As you know, all the element chapters follow the same structure, as outlined on the slide. To avoid having to translate the same section headings hundreds of time, the headings will be translated only once in a table in RDA’s Content Management System. The table will then be used to insert the French headings in the French files that translators will be working on.
  • Another objective of the 3R Project was to convert the RDA Toolkit data to the DITA format, which was implemented in 2017.
    The boilerplate file, as we call it, is an example of how the DITA format improved content management and the translation process.
    The file contains sentences and paragraphs that are frequently re-used in the RDA text. It is in fact an improved and more granular version of the recurring phrases document that I mentioned earlier.
    When needed in a specific instruction, boilerplate text is pulled into RDA instructions using content references or content key references.
    Re-used content is therefore only translated once. If revisions or corrections are needed, they will only need to be done once.



  • The boilerplate file contains more than 250 sentences or paragraphs of which the slide shows a very small sample. The fact that conditions and options are formulated as separate sentences in the new Toolkit helps take advantage of the boilerplate technique.
  • As of May 26, RDA had a little more than 3000 elements. Instructions for 84% of the elements are composed entirely of boilerplate and will be translated automatically. The element “printer agent of” is one of these elements.
    This means that only instructions for 481 elements (that is 16%) will have to be translated by a translator.


    The figures have been provided by RSC Secretary Linda Barnhart.
  • One issue that we had to tackle when translating RDA Reference was the removal of parentheses in element names. In the current Toolkit, parentheses are used to qualify similar labels by element range but this practice was found inconsistent and confusing in the English version and was discontinued.
    In English, it is not difficult to remove the parentheses and produce a satisfactory result without changing the word order.
    This does not work so easily in French where removing the parentheses requires changing the word order and using an adjective. Appropriate adjectives are not always available and those that are may sound pedantic or inappropriate; changing the word order also means that the most significant word will no longer be the first, which is not an issue in English.
    It was therefore decided to retain parentheses in some instances for consistency and to keep a more useful order where the entry is under the specific term and not the entity.
  • One probably never looks at a text more closely than when one has to translate it and RDA translators have proved to be good proofreaders. During the process of translating RDA Reference, we encountered and reported several editorial problems such as typos and inconsistencies between similar definitions. We also made suggestions to revise the English text whenever a clarification was needed to produce an accurate translation.

    We also reported more significant problems with some of the definitions. For example, the element coordinates of cartographic content was an attribute in the original Toolkit and became a relationship element in the beta Toolkit with Place as range. The original definition in the beta Toolkit did not reflect the change by defining the element as a place. This was fixed during the 3R Project.
  • The word issue and its cognates raise problems. Their meanings are difficult to grasp for a Francophone. For example, does issuing cover only publication? Most reference sources consulted seem to suggest so but its usage in RDA and in terms such as issuing body agent seem to indicate otherwise. What is the distinction between publication, release and issuance in a scope note such as the one for name of publisher, which reads “Publication includes release and issuance”? The distinction seems subtle enough to confuse Google translate which suggested, back in July 2019, a translation that meant “Publication includes publication and publication.”

    The element issuing body agent and its narrower elements pose their own difficulties. Issuing body used to refer only to a corporate body under AACR2. How to translate issuing body when the term applies to all types of agents? Could body be omitted to avoid confusion and facilitate translation?

  • As I mentioned earlier, the French translation team still has some work to do to complete the translation of RDA Reference. Over the past year, we have had to devote time and resources to another major project and this forced us to put the translation on hold for a while. We therefore still have several steps to go through. We set the end of May 2021 as our target date to complete the translation of the new RDA.
  • If you want to learn more about the original French translation project, you can refer to the article that Clément Arsenault, Pat Riva and I wrote for Cataloging & Classification Quarterly in 2014.

×
https://www.slideshare.net/jhennelly/nardac-rda-update-forum-8320
www.slideshare.net
crawl=CC-MAIN-2022-40
462434
application/http; msgtype=response
sha1:PRCFRKKVVIEJS63YWSONCU5YKGHMHVFF
<urn:uuid:5bf0031f-20f1-440c-bb91-82b22eb9ba67>
2022-09-28T20:20:13Z
146.75.34.152
text/html
sha1:OCVNRN6HF6KWMLWGIRC63DTJ732OWELZ
<urn:uuid:b69d1067-af31-422b-af6b-4b92f5ae9842>
https://www.slideshare.net/jhennelly/nardac-rda-update-forum-8320
response
<urn:uuid:0b90b5ca-9df9-4a32-af94-14949983adff>
isPartOf: CC-MAIN-2022-40
publisher: Common Crawl
description: Wide crawl of the web for September/October 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-12
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/