Diving in Panama Papers and Open Data to Discover Emerging NewsOntotext
Get guidance through the gigantic sea of freely released data from Panama Papers as well as Linked Open Data could. You will learn how it can empower you understanding of today’s news or any other information source.
How to Reveal Hidden Relationships in Data and Risk AnalyticsOntotext
Imagine risk analysis manager or compliance officer who can discover easily relationships like this: Big Bucks Café out of Seattle controls My Local Café in NYC through an offshore company. Such discovery can be a game changer if My Local Café pretends to be an independent small enterprise, while recently Big Bucks experiences financial difficulties.
Gain Super Powers in Data Science: Relationship Discovery Across Public DataOntotext
The document summarizes a webinar on relationship discovery across public data. It outlines the webinar agenda which includes use cases of relation discovery and media monitoring. It also describes examples of relationship discovery from datasets like the Panama Papers and media monitoring examples. It discusses linking news to knowledge graphs and semantic media monitoring. Finally, it covers mapping additional datasets to DBPedia to facilitate relationship discovery.
DI Courthouse is a searchable digital database of real property records and documents that provides immediate 24/7 access to detailed records. This allows users to determine property ownership while significantly reducing time spent searching antiquated paper records at courthouses. The database indexes records to allow searching by attributes not previously available. Users can search specific surveys, sections, lots or blocks to find relevant documents. Records in some counties date back to sovereignty.
The new RDA: resource description in libraries and beyond / Gordon DunsireCILIP MDG
This document discusses the new RDA (Resource Description and Access), which provides data elements, guidelines and instructions for creating metadata for library and cultural heritage resources. Key points:
- The RDA Toolkit provides user-focused elements, guidelines and instructions. The RDA Registry provides infrastructure for well-formed, linked RDA data applications.
- There are now 13 entities and over 1700 elements in RDA. Elements are now the main unit of focus and have standard structure/layout.
- Recording methods have been extended to all elements and now make the linked data method explicit. Instructions are now more optional to accommodate local practice.
- Effective description requires choosing appropriate entities and elements based on an application profile
Chris Oliver: RDA: Designed for Current and Future EnvironmentsALATechSource
RDA is a new metadata standard that replaces AACR2 and provides guidelines for recording bibliographic data to support resource discovery. It is designed to work in current catalogues and databases, as well as take advantage of new technologies through a flexible framework aligned with FRBR and FRAD models. RDA defines discrete data elements that provide precise, machine-actionable data to describe resources and their relationships.
Handout 2 for Metadata for Visual ResourcesJenn Riley
Riley, Jenn. "Metadata for Visual Resources." Summer Educational Institute for Visual Resources and Image Management, University of New Mexico, June 9, 2011.
Diving in Panama Papers and Open Data to Discover Emerging NewsOntotext
Get guidance through the gigantic sea of freely released data from Panama Papers as well as Linked Open Data could. You will learn how it can empower you understanding of today’s news or any other information source.
How to Reveal Hidden Relationships in Data and Risk AnalyticsOntotext
Imagine risk analysis manager or compliance officer who can discover easily relationships like this: Big Bucks Café out of Seattle controls My Local Café in NYC through an offshore company. Such discovery can be a game changer if My Local Café pretends to be an independent small enterprise, while recently Big Bucks experiences financial difficulties.
Gain Super Powers in Data Science: Relationship Discovery Across Public DataOntotext
The document summarizes a webinar on relationship discovery across public data. It outlines the webinar agenda which includes use cases of relation discovery and media monitoring. It also describes examples of relationship discovery from datasets like the Panama Papers and media monitoring examples. It discusses linking news to knowledge graphs and semantic media monitoring. Finally, it covers mapping additional datasets to DBPedia to facilitate relationship discovery.
DI Courthouse is a searchable digital database of real property records and documents that provides immediate 24/7 access to detailed records. This allows users to determine property ownership while significantly reducing time spent searching antiquated paper records at courthouses. The database indexes records to allow searching by attributes not previously available. Users can search specific surveys, sections, lots or blocks to find relevant documents. Records in some counties date back to sovereignty.
The new RDA: resource description in libraries and beyond / Gordon DunsireCILIP MDG
This document discusses the new RDA (Resource Description and Access), which provides data elements, guidelines and instructions for creating metadata for library and cultural heritage resources. Key points:
- The RDA Toolkit provides user-focused elements, guidelines and instructions. The RDA Registry provides infrastructure for well-formed, linked RDA data applications.
- There are now 13 entities and over 1700 elements in RDA. Elements are now the main unit of focus and have standard structure/layout.
- Recording methods have been extended to all elements and now make the linked data method explicit. Instructions are now more optional to accommodate local practice.
- Effective description requires choosing appropriate entities and elements based on an application profile
Chris Oliver: RDA: Designed for Current and Future EnvironmentsALATechSource
RDA is a new metadata standard that replaces AACR2 and provides guidelines for recording bibliographic data to support resource discovery. It is designed to work in current catalogues and databases, as well as take advantage of new technologies through a flexible framework aligned with FRBR and FRAD models. RDA defines discrete data elements that provide precise, machine-actionable data to describe resources and their relationships.
Handout 2 for Metadata for Visual ResourcesJenn Riley
Riley, Jenn. "Metadata for Visual Resources." Summer Educational Institute for Visual Resources and Image Management, University of New Mexico, June 9, 2011.
The document discusses metadata schemas and standards for digital library projects in China. It describes several existing metadata schemes including the General Format for Digitalized Chinese Full-text (GFDCF), the CPDLP Metadata Profiles, and the Chinese Metadata Specifications (CMS). It also discusses applying ontologies to build a unified metadata framework, including ontologies of Chinese information resources and bibliographic relations. This would help address issues of lack of unified semantics, mappings between schemas, and diversification in the Chinese metadata landscape.
The document discusses master data management in the city of Gothenburg. It describes challenges around managing structured and unstructured data from multiple systems. It then demonstrates a pilot project that uses semantic standards, models and open vocabularies to link and query master data. Entities like people, organizations, locations and services are modeled. The pilot shows how data can be accessed through a SPARQL endpoint or API to enable interoperability.
Invited report in Proceedings of "Digital Presentation and Preservation of Cultural and Scientific Heritage" (DiPP2012) conference, September 2012, Veliko Tarnovo, Bulgaria.
The document discusses Resource Description and Access (RDA), a new cataloging standard that aims to improve findability, identification, and interoperability of library resources. RDA is based on FRBR (Functional Requirements for Bibliographic Records) and FRAD (Functional Requirements for Authority Data) models. It defines cataloging entities and relationships using Semantic Web technologies like URIs, RDF, and SKOS to make metadata more reusable and linkable on the global scale. The document outlines how RDA entities, elements, and vocabularies are being registered in the NSDL Metadata Registry to enable their representation and sharing using Semantic Web formats.
The document discusses the development of a core data model for an organization to guide system development, enable review of potential applications, and provide a basis for interoperability. It identifies four fundamental data classes and two key initial services focused on research projects and identity management. Stakeholders have provided positive feedback and support moving forward with an immediate focus on a lightweight request record system and integrating various data sets.
The workshop focuses on constructing authorized access points for records under RDA, utilizing the LC/PCC Policy Statements (LCC/PCC PS). This is NOT a NACO workshop. Authorized access points for personal names, corporate bodies, conferences, and works and expressions (titles) will be covered, as will relationship designators for personal names and corporate bodies. Subject headings will not be covered.
Slides used to introduce the technical aspects of DSpace-CRIS to the technical staff of the Hamburg University of Technology.
Main topics:
The DSpace-CRIS data model: additional entities, interactions with the DSpace data model (authority framework), enhanced metadata, inverse relationship
ORCID integration & technical details: available features & use cases (authentication, authorization, profile claiming, profile synchronization push & pull, registry lookup), configuration, API-KEY, use of the sandbox, metadata mapping
FRBR RDA MARC format for cataloguing andYesan Sellan
This document discusses how MARC 21 fields relate to FRBR entities and RDA attributes. It provides examples of how attributes of works, expressions, and manifestations are recorded in MARC fields and explains how RDA differs from AACR2 in its conceptual model and treatment of access points. New fields are introduced in RDA to record attributes at the work, expression, and manifestation levels in a more granular way. Relationships between entities are conveyed through notes and linking fields.
Boost your data analytics with open data and public news contentOntotext
Get guidance through the gigantic sea of freely available Open Data and learn how it can empower you analysis of any kind of sources.
This webinar is a live demo of news and data analytics, based on rich links within big knowledge graphs. It will show you how to:
Build ranking reports (e.g for people and organisations)
View topics linked implicitly (e.g. daughter companies, key personnel, products …)
Draw trend lines
Extend your analytics with additional data sources
Miksa s cmr presentation_tla19_18apr2019ShawneMiksa
Presentation given by Dr Shawne Miksa at 2019 Texas Library Association (TLA) Annual Conference for the Cataloging and Metadata Roundtable (CMR) panel presentation "An RDA Status Report and Update on New Toolkit", April 18, 2019 in Austin, TX.
The document discusses understanding data through deconstructing it, representing relationships between entities, and accessing data independently of format or location. It describes how entities and relationships are denoted using identifiers and expressed using languages. Relationships are represented using notations like graphs, tables, and serialization formats, and persisted in documents. Data access requires identifiers for entities, relationships, and descriptors along with resolution of data source names using protocols like DNS and HTTP to provide independence from systems.
Tools of our Trade (RDA, MARC21) 2010-03-15Ann Chapman
UKOLN is supported by various organizations. The document discusses tools for resource description like AACR2/RDA and MARC standards. It provides an overview of the development of RDA as the new cataloging standard to replace AACR2, including the goals, structure and timeline of RDA. The relationship between RDA and MARC 21 is also covered.
This document provides an introduction and overview of Resource Description and Access (RDA), the new cataloging standard that replaces Anglo-American Cataloguing Rules (AACR). RDA is designed for the digital age and is based on Functional Requirements for Bibliographic Records (FRBR) and Functional Requirements for Authority Data (FRAD). RDA provides more flexibility and is compatible with current metadata standards and encoding formats like MARC. While RDA has some advantages, there are also ongoing considerations and discussions around its implementation.
Future directions for RDA / Gordon DunsireCILIP MDG
The document discusses future directions for the Resource Description and Access (RDA) standard. It outlines strategies for expanding RDA communities internationally and in cultural heritage domains. It also describes plans to consolidate FRBR models, develop related standards, and reorganize the RDA Toolkit. Additionally, it discusses developing a new RDA reference data infrastructure to support multiple services and applying the Linked Data approach. The impact of the new FRBR-LRM conceptual model on RDA is also addressed.
The students in an LS 566 Metadata class were asked to index a collection of six images from the 1992 University of Alabama Crimson Tide football season. The class chose a modified Dublin Core metadata schema containing 15 elements to describe the images. Students worked in groups to define the elements and map them to the images. They used Omeka software to extract image text and connect files to element fields. The indexing process took longer than expected due to a tornado that damaged the university.
Engaging with RDA: governance and strategyGordon Dunsire
The document discusses RDA's governance and strategy review. Key points include:
- The governance structure is being revised to increase international representation on committees to better support RDA's role as a global standard.
- A new RDA Board and revised Steering Committee structure will be implemented by 2020 to reflect different communities.
- A five-year strategic plan through 2020 aims to increase RDA adoption internationally and develop a sustainable business model.
- Strategies include making RDA truly multilingual and expanding its use for linked data and cultural heritage institutions.
This document discusses approaches to developing globally interoperable metadata standards like RDA. It describes the failure of top-down approaches and issues with both top-down and bottom-up mapping strategies. Bottom-up risks multiple overlapping element sets while top-down may not fully represent local practices. The author advocates balancing global needs with flexibility for local implementation.
The document discusses metadata schemas and standards for digital library projects in China. It describes several existing metadata schemes including the General Format for Digitalized Chinese Full-text (GFDCF), the CPDLP Metadata Profiles, and the Chinese Metadata Specifications (CMS). It also discusses applying ontologies to build a unified metadata framework, including ontologies of Chinese information resources and bibliographic relations. This would help address issues of lack of unified semantics, mappings between schemas, and diversification in the Chinese metadata landscape.
The document discusses master data management in the city of Gothenburg. It describes challenges around managing structured and unstructured data from multiple systems. It then demonstrates a pilot project that uses semantic standards, models and open vocabularies to link and query master data. Entities like people, organizations, locations and services are modeled. The pilot shows how data can be accessed through a SPARQL endpoint or API to enable interoperability.
Invited report in Proceedings of "Digital Presentation and Preservation of Cultural and Scientific Heritage" (DiPP2012) conference, September 2012, Veliko Tarnovo, Bulgaria.
The document discusses Resource Description and Access (RDA), a new cataloging standard that aims to improve findability, identification, and interoperability of library resources. RDA is based on FRBR (Functional Requirements for Bibliographic Records) and FRAD (Functional Requirements for Authority Data) models. It defines cataloging entities and relationships using Semantic Web technologies like URIs, RDF, and SKOS to make metadata more reusable and linkable on the global scale. The document outlines how RDA entities, elements, and vocabularies are being registered in the NSDL Metadata Registry to enable their representation and sharing using Semantic Web formats.
The document discusses the development of a core data model for an organization to guide system development, enable review of potential applications, and provide a basis for interoperability. It identifies four fundamental data classes and two key initial services focused on research projects and identity management. Stakeholders have provided positive feedback and support moving forward with an immediate focus on a lightweight request record system and integrating various data sets.
The workshop focuses on constructing authorized access points for records under RDA, utilizing the LC/PCC Policy Statements (LCC/PCC PS). This is NOT a NACO workshop. Authorized access points for personal names, corporate bodies, conferences, and works and expressions (titles) will be covered, as will relationship designators for personal names and corporate bodies. Subject headings will not be covered.
Slides used to introduce the technical aspects of DSpace-CRIS to the technical staff of the Hamburg University of Technology.
Main topics:
The DSpace-CRIS data model: additional entities, interactions with the DSpace data model (authority framework), enhanced metadata, inverse relationship
ORCID integration & technical details: available features & use cases (authentication, authorization, profile claiming, profile synchronization push & pull, registry lookup), configuration, API-KEY, use of the sandbox, metadata mapping
FRBR RDA MARC format for cataloguing andYesan Sellan
This document discusses how MARC 21 fields relate to FRBR entities and RDA attributes. It provides examples of how attributes of works, expressions, and manifestations are recorded in MARC fields and explains how RDA differs from AACR2 in its conceptual model and treatment of access points. New fields are introduced in RDA to record attributes at the work, expression, and manifestation levels in a more granular way. Relationships between entities are conveyed through notes and linking fields.
Boost your data analytics with open data and public news contentOntotext
Get guidance through the gigantic sea of freely available Open Data and learn how it can empower you analysis of any kind of sources.
This webinar is a live demo of news and data analytics, based on rich links within big knowledge graphs. It will show you how to:
Build ranking reports (e.g for people and organisations)
View topics linked implicitly (e.g. daughter companies, key personnel, products …)
Draw trend lines
Extend your analytics with additional data sources
Miksa s cmr presentation_tla19_18apr2019ShawneMiksa
Presentation given by Dr Shawne Miksa at 2019 Texas Library Association (TLA) Annual Conference for the Cataloging and Metadata Roundtable (CMR) panel presentation "An RDA Status Report and Update on New Toolkit", April 18, 2019 in Austin, TX.
The document discusses understanding data through deconstructing it, representing relationships between entities, and accessing data independently of format or location. It describes how entities and relationships are denoted using identifiers and expressed using languages. Relationships are represented using notations like graphs, tables, and serialization formats, and persisted in documents. Data access requires identifiers for entities, relationships, and descriptors along with resolution of data source names using protocols like DNS and HTTP to provide independence from systems.
Tools of our Trade (RDA, MARC21) 2010-03-15Ann Chapman
UKOLN is supported by various organizations. The document discusses tools for resource description like AACR2/RDA and MARC standards. It provides an overview of the development of RDA as the new cataloging standard to replace AACR2, including the goals, structure and timeline of RDA. The relationship between RDA and MARC 21 is also covered.
This document provides an introduction and overview of Resource Description and Access (RDA), the new cataloging standard that replaces Anglo-American Cataloguing Rules (AACR). RDA is designed for the digital age and is based on Functional Requirements for Bibliographic Records (FRBR) and Functional Requirements for Authority Data (FRAD). RDA provides more flexibility and is compatible with current metadata standards and encoding formats like MARC. While RDA has some advantages, there are also ongoing considerations and discussions around its implementation.
Future directions for RDA / Gordon DunsireCILIP MDG
The document discusses future directions for the Resource Description and Access (RDA) standard. It outlines strategies for expanding RDA communities internationally and in cultural heritage domains. It also describes plans to consolidate FRBR models, develop related standards, and reorganize the RDA Toolkit. Additionally, it discusses developing a new RDA reference data infrastructure to support multiple services and applying the Linked Data approach. The impact of the new FRBR-LRM conceptual model on RDA is also addressed.
The students in an LS 566 Metadata class were asked to index a collection of six images from the 1992 University of Alabama Crimson Tide football season. The class chose a modified Dublin Core metadata schema containing 15 elements to describe the images. Students worked in groups to define the elements and map them to the images. They used Omeka software to extract image text and connect files to element fields. The indexing process took longer than expected due to a tornado that damaged the university.
Engaging with RDA: governance and strategyGordon Dunsire
The document discusses RDA's governance and strategy review. Key points include:
- The governance structure is being revised to increase international representation on committees to better support RDA's role as a global standard.
- A new RDA Board and revised Steering Committee structure will be implemented by 2020 to reflect different communities.
- A five-year strategic plan through 2020 aims to increase RDA adoption internationally and develop a sustainable business model.
- Strategies include making RDA truly multilingual and expanding its use for linked data and cultural heritage institutions.
This document discusses approaches to developing globally interoperable metadata standards like RDA. It describes the failure of top-down approaches and issues with both top-down and bottom-up mapping strategies. Bottom-up risks multiple overlapping element sets while top-down may not fully represent local practices. The author advocates balancing global needs with flexibility for local implementation.
RDA, MARC and BIBFRAME: transition and interactionGordon Dunsire
This document discusses the transition and interaction between RDA, MARC, and BIBFRAME. It provides mappings between the FRBR/FRAD and RDA entities and relationships to BIBFRAME properties. It also maps ISBD and MARC21 entities and relationships to RDA and BIBFRAME elements to show how descriptive data moves from description to access in linked data models.
An RDA record is a set of machine-readable identifiers and human-readable text that represents an entity such as a work, expression, manifestation, or item. It includes attributes like titles and identifiers, and relationships to other entities. The specific attributes and relationships included in a record depend on the needs of the application using it. RDA aims to support linked data applications by providing structured, linkable descriptions of cultural works and their relationships.
The UNIMARC in RDF project aims to represent the UNIMARC format, including its structures and controlled terminology code lists, in RDF to make it accessible as linked data. It is funded for the first year by the Permanent UNIMARC Committee. The current focus is the UNIMARC Bibliographic format. The project will take more than one year to complete additional tasks such as mapping UNIMARC elements to reflect internal semantics and interoperate with other bibliographic formats.
Shrinking the silo boundary: data and schema in the Semantic WebGordon Dunsire
This document discusses representing local structured metadata as linked data in the Semantic Web. It notes that mapping from a local schema like MARC 21 to global linked data schemas can result in lost information. To avoid this, the document recommends publishing the local schema as its own RDF element set. This allows the local data and schema to be published as linked data without information loss, while still enabling mappings to other schemas. It presents advantages like other communities being able to understand and reuse the local schema. The document concludes by visualizing how this approach "shrinks the silo" by publishing the local data, schema, and mappings as RDF on the Semantic Web.
Multilingual issues in the representation of international bibliographic stan...Gordon Dunsire
The document discusses multilingual issues in representing international bibliographic standards for the semantic web. It outlines IFLA's standards for bibliographic data and its namespace used to represent the standards and vocabularies as RDF. Translating the standards into different languages exposed challenges regarding scope, style, source documentation, disambiguation, and language inflection. The presentation calls for authoritative translations of cataloguing standards and related documents in 26+ languages.
Mapping FRBR, ISBD, RDA, and other namespaces to DC for interoperabilityGordon Dunsire
This document summarizes Gordon Dunsire's presentation on mapping namespaces like FRBR, ISBD, RDA and others to Dublin Core for interoperability. It discusses Dublin Core's origins and intention as a model, the proliferation of richer schemas, and mapping and the sub-property ladder approach. It provides examples of mapping properties from ISBD, RDA, MARC21 and Dublin Core and discusses semantic constraints, reasoning, and interoperability. It also touches on BIBFRAME, schema.org and their roles in relation to Dublin Core mappings.
The document discusses the concept of granularity as it relates to linked open data from libraries, noting that data can have different levels of granularity depending on the level of description and complexity of the schema. It provides examples of how granularity applies to different aspects of bibliographic records and semantic mappings between properties from different schemas. The document also demonstrates how semantic reasoning can be used to infer additional statements based on sub-properties and property domains.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdfTechgropse Pvt.Ltd.
In this blog post, we'll delve into the intersection of AI and app development in Saudi Arabia, focusing on the food delivery sector. We'll explore how AI is revolutionizing the way Saudi consumers order food, how restaurants manage their operations, and how delivery partners navigate the bustling streets of cities like Riyadh, Jeddah, and Dammam. Through real-world case studies, we'll showcase how leading Saudi food delivery apps are leveraging AI to redefine convenience, personalization, and efficiency.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Things to Consider When Choosing a Website Developer for your Website | FODUUFODUU
Choosing the right website developer is crucial for your business. This article covers essential factors to consider, including experience, portfolio, technical skills, communication, pricing, reputation & reviews, cost and budget considerations and post-launch support. Make an informed decision to ensure your website meets your business goals.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
1. July 22, 20181
RDA and MARC 21
Gordon Dunsire, James Hennelly, Thurstan Young
Presented at “RDA and MARC 21”
June 25, 2018, New Orleans, USA
The impact of the 3R Project
2. RDA and data encoding July 22, 20182
RDA and data encoding
Gordon Dunsire, Chair, RSC
The impact of the 3R Project
3. RDA and data encoding July 22, 20183
3R Project
RDA Toolkit Restructure and Redesign
Project
New responsive design and structure
Impact of the IFLA Library Reference Model
(LRM)
RDA strategy for international, cultural heritage,
and linked data communities
4. RDA and data encoding July 22, 20184
Beta Toolkit
Beta version of the new RDA Toolkit
released June 13, 2018
Transformation of guidance and instructions
is ongoing; expected completion December
2018
Development of entities, elements, and
terminologies almost complete
5. RDA and data encoding July 22, 20185
LRM entities
New entities for Agent, Collective Agent,
Nomen, Place, Timespan
Many attributes become relationships
Example: date of birth [of Person]
=> Related timespan of person
More inverse relationships
Date of birth of [related person of
timespan]
6. RDA and data encoding July 22, 20186
The numbers
13 entities 1700+ elements
Work 388 Agent 175
Expression 291 Person 85
Manifestation 282 Collective Agent 34
Item 70 Corporate Body 84
Place 45 Family 46
Timespan 54 Nomen 169
RDA Entity 27
7. RDA and data encoding July 22, 20187
RDA entities
RDA Corporate Body and Family are types
of Collective Agent
Person restricted to human beings
Does not cover “non-human personages”
No change for Work, Expression,
Manifestation, Place
Item always exemplifies a manifestation
8. RDA and data encoding
Kinds of recorded data
RDA is designed
to support a
wide range of
data carrier
architectures
for storage and
display
Flat-file: card and
other print-based
catalogues
Bib/Authority:
MARC, etc.
RDBMS: Table for each
entity, row keys (IDs)
RDF: Classes,
properties, and IRIs
Local
(Closed-
world)
Global
(Open-
world)
9. RDA and data encoding July 22, 20189
Recording methods
Latent in current instructions
Explicit in the new Toolkit
Cover the basic kinds of data recording
Accommodate data from outside the
professional cataloguing environment
The metadata deluge
Provide choices to suit applications and costs
10. RDA and data encoding July 22, 201810
Unstructured description
11. RDA and data encoding July 22, 201811
Structured description
12. RDA and data encoding July 22, 201812
Identifier
13. RDA and data encoding July 22, 201813
[Linked data] IRI
14. RDA and data encoding July 22, 201814
Data provenance
15. RDA and data encoding July 22, 201815
RDA uses RDF to record data for RDA Reference
(entities, elements, and vocabulary encoding
schemes)
• Provides data for RDA Toolkit (Glossary,
element reference, navigation)
• Available from RDA Registry under open
license
RDA in RDF
16. RDA and data encoding
Recording methods for
related data
RDA Entity
1
RDA Entity
2
is related to
"identifier for related entity 2"
"note on related entity 2"
"access point for related entity 2"
Keyword index
Authority file
Standard
identifier system
Semantic Web
17. MARC 21 in RDA July 22, 201817
MARC 21 in RDA Toolkit
James Hennelly, Director, ALA Digital
Reference
18. MARC 21 in RDA July 22, 201818
Map input form
Spreadsheet/csv file
Better than a wordprocessor …
Output mappingInput fieldsRegistry RDF
19. MARC 21 in RDA July 22, 201819
Strings
No MARC 21 in RDF to link to
StringNo thing
rdaa:P50001 rdakit:hasM21 "MARC 21 Authority 100 $a" .
Predicate
(thing)
Subject
(thing)
Object
(string)
20. MARC 21 in RDA July 22, 201820
Toolkit display
21. MARC 21 in RDA 22/07/201821
Search: authority 100
First 3 of 10 found
22. RDA in MARC 21:
Accommodating 3R
A presentation by Thurstan Young,
U.K. Representative to the MARC Advisory Committee
Thurstan YoungJune 2018
23. Context for change (RDA)
3R Project Timeline
New RDA Entities
New RDA Guidance
24. Context for change (MARC 21)
Existing MARC 21 content designation
New MARC21 content designation
Emerging non-MARC data formats
25. Basic Principles
Choice of MARC 21 format: bibliographic, authority,
other?
Granularity: record; field; subfield level?
Consistency: equivalent field by field content
designation?
Utility: is change helpful?
Feasibility: is change possible within format constraints?
26. 3R Project Timeline (13th June deliverables)
An initial implementation of LRM
Reorganized RDA instructions
Redesigned Personal and Institutional Profile capabilities
Search and navigation functions
Cross-Reference and Cross-Reference Preview functions
Ready Reference feature for each RDA element
27. 3R Project Timeline (post 13th June)
Revisions to the RDA standard
Introduction of a graphical browse tool
Translations of the RDA standard
Introduction of policy statements and integrated display
29. New Entities : RDA Entity
RDA Entity : “An abstract class of key conceptual objects
in the universe of human discourse that is a focus of
interest to users of RDA metadata in library information
systems. An RDA entity includes an agent, collective
agent, corporate body, expression, family, item,
manifestation, nomen, person, place, timespan, and
work.”
30. RDA Entity:
Content designation
No content designation present in MARC 21
Accommodation seems unnecessary since it’s function is
to support high-level semantics in the RDA/LRM ontology
31. New Entities : Nomen
Nomen : “A designation that refers to an RDA entity. A
designation includes a name, title, access point,
identifier, and subject classification codes and headings.”
32. Nomen:
Content designation
No content designation present in MARC 21
New content designation would be necessary to separate
names and identifiers for those names from the entities
which they identify
In principle, each form of name and identifier for that
name would require a separate record and unique
identifier and its own attributes, such as provenance,
could be recorded. In a MARC context, an authority
record has to have a unique identifier, but the RCN could
not be an identifier for the name
In practice accommodation may be too disruptive to the
structure of current authority files
33. Nomen:
Possible implementation scenarios
Split authorities into two separate records : one for
names and identifiers and another for attributes of the
entity
Split authorities into separate records for each authorized
name, variant name, identifier and for attributes of the
entity
34. New Entities : Place
Place : “A given extent of space.”
42. Unstructured description
Recording methods include:
Manifestation statement (New)
Unstructured note
Name or title in direct order, as it appears in sources of
information
Uncontrolled term for a concept
43. Manifestation statements : Guidance
A manifestation may carry information that describes the
manifestation itself.
This information is recorded to follow the principle of
representation.
A manifestation statement supports the user task identify.
A manifestation statement is recorded only as an
unstructured description.
44. Manifestation statements : Elements
Manifestation copyright statement
Manifestation designation of serial statement
Manifestation dissertation statement
Manifestation distribution statement
Manifestation edition statement
Manifestation frequency statement
Manifestation identifier statement
Manifestation manufacture statement
Manifestation production statement
Manifestation publication statement
Manifestation regional encoding statement
Manifestation series statement
Manifestation title and responsibility statement
45. Manifestation statements : Example (1)
Sample title page layout:
Archaeological Ceramics:
A Review of Current Research
Edited by
Simona Scarcella
BAR International Series 2193
46. Manifestation statements : Example (2)
Title page detail:
Archaeological Ceramics:
A Review of Current Research
Edited by
Simona Scarcella
Manifestation title and responsibility statement:
Archaeological ceramics: A Review of Current Research Edited by Simona Scarcella
MARC 21 Title statement:
245 00 $a Archaeological Ceramics : $b A Review of Current Research / $c Edited
by Simona Scarcella
47. Manifestation statements : Example (3)
Title page detail:
BAR International Series 2193
Manifestation series statement:
BAR International Series 2193
MARC 21 Series statement:
490 0# $a BAR International Series; $v 2193
48. Manifestation statements :
Content designation
No content designation present in MARC 21
Existing content designation too granular
Free text strings broken down into separate sub-
elements
Manifestation level data : MARC 21 bibliographic format
49. Manifestation statements :
New content designation options
Indicator / subfield level:
New indicators added to existing 0XX / 2XX / 3XX / 4XX / 5XX
fields (e.g. a manifestation title and statement of responsibility
statement ; manifestation series statement)
OR
New subfields added to existing 0XX / 2XX / 3XX / 4XX / 5XX
fields
Field level:
New 0XX / 2XX / 3XX / 4XX / 5XX fields in bibliographic format
(e.g. a title page composed of undifferentiated manifestation
statements)
Redefine existing fields to carry manifestation statements
and new fields to carry more granular elements.
50. Manifestation statements :
Option 1 (Indicator)
Manifestation title and responsibility statement:
Archaeological Ceramics: A Review of Current Research Edited by Simona
Scarcella
MARC 21 Title statement:
245 20 $a Archaeological Ceramics: A Review of Current Research Edited by
Simona Scarcella
New 245 1st indicator specifies that subfield $a contains
manifestation title and responsibility statement (not only title proper).
51. Manifestation statements :
Option 2 (Subfield)
Manifestation title and responsibility statement:
Archaeological Ceramics: A Review of Current Research Edited by Simona
Scarcella
MARC 21 Title statement:
245 00 $m Archaeological Ceramics: A Review of Current Research Edited by
Simona Scarcella
New 245 $m specifies that subfield contains manifestation title and
responsibility statement.
52. Manifestation statements :
Option 3 (Field)
Manifestation statement:
Archaeological Ceramics: A Review of Current Research Edited by Simona
Scarcella BAR International Series 2193
MARC 21 Manifestation statement:
241 00 $a Archaeological Ceramics: A Review of Current Research Edited by
Simona Scarcella BAR International Series 2193
New 241 tag specifies that field contains an undifferentiated
manifestation statement.
53. Manifestation statements :
Option 4 (Redefinition)
Manifestation statement:
Archaeological Ceramics: A Review of Current Research Edited by Simona
Scarcella BAR International Series 2193
MARC 21 Manifestation statement:
241 00 $a Archaeological ceramics : $b a review of current research / $c edited by
Simona Scarcella
245 00 $a Archaeological Ceramics: A Review of Current Research Edited by
Simona Scarcella BAR International Series 2193
New 241 tag carries elements previously accommodated in 245; 245
tag redefined to contain an undifferentiated manifestation statement.
54. Manifestation Statements : MARC 21
Indicator / Subfield Change Candidates (1)
RDA Element MARC Bibliographic
Manifestation copyright statement 260
264 2nd Ind. 4
Manifestation designation of serial
statement
362
Manifestation dissertation statement 502
Manifestation distribution statement 260
264 2nd Ind. 2
Manifestation edition statement 250
55. Manifestation Statements : MARC 21
Indicator / Subfield Change Candidates (2)
RDA Element MARC Bibliographic
Manifestation frequency statement 310
Manifestation identifier statement 020
022
024
026
028
030
032
037
074
086
502
56. Manifestation Statements : MARC 21
Indicator / Subfield Change Candidates (3)
RDA Element MARC Bibliographic
Manifestation manufacture
statement
260
264 2nd Ind 3
Manifestation production statement 260
264 2nd Ind 0
Manifestation publication statement 260
264 2nd Ind 1
Manifestation regional encoding
statement
538
Manifestation series statement 490
Manifestation title and responsibility
statement
245
57. Manifestation statements :
Utility / Feasibility of Change
New content designation would allow the encoding of
whole or partial title page content, etc. using scanned
data (e.g. recorded using light pen)
New content designation would allow the exact
transcription of statements for early printed resources
(e.g. complex publication / distribution and manufacture
statements)
Sufficient content designation is still available to record
manifestation statements (although not consistently field
by field)
58. Representative Expressions : Guidance
A representative expression provides the values of
specific elements used to identify a work and distinguish
it from other works.
Any expression can be used as a representative
expression.
59. Representative Expressions Elements for Works
Aspect ratio of representative expression
Colour content of representative expression
Content type of representative expression
Date of capture of representative expression
Duration of representative expression
Extent of representative expression
Intended audience of representative expression
Key of representative expression
Language of representative expression
Medium of performance of representative expression
Place of capture of representative expression
Projection of cartographic content of representative expression
Scale of representative expression
Script of representative expression
Sound content of representative expression
60. Representative Expression Elements :
Example (1)
Sample Work Record:
Creator of work: Charles Dickens
Preferred title of work: Great expectations
Language of representative expression: English
MARC 21 Authority Record :
075 ## $a Work $2 rdaw*
100 1# $a Dickens, Charles, $d 1812-1870. $t Great expectations
377 ## $a eng
* Note that an 075 $2 source code has yet to be defined for RDA Work
properties; here it is modelled on the curie prefix specified in the RDA
Registry.
61. Representative Expressions Elements:
Example (2)
Sample Work Record :
Creator of work: Wolfgang Amadeus Mozart
Preferred title of work: Divertimenti
Key of representative expression: D major
Thematic index number: K. 251
MARC 21 Authority Record:
075 ## $a Work $2 rdaw
100 1# $a Mozart, Wolfgang Amadeus, 1756-2791. $t Divertimenti, $n K. 251, $r D
major
383 ## $c K. 251
384 0# $a D major
62. Representative Expression Elements :
Example (3)
Sample Work Record :
Creator of work: Louise Penny
Preferred title of work: Trick of the light
Language of representative expression: English
Representative expression: Penny, Louise. Trick of the light. 2011
MARC 21 Authority Record :
075 ## $a Work $2 rdaw
100 1# $a Penny, Louise. $t Trick of the light
377 ## $a eng
500 1# $w r $i Representative expression: $a Penny, Louise. $t Trick of the light. $f
2011
63. Representative Expression Elements :
Content designation
No content designation present in MARC 21
Existing content designation for elements that could be
use to record representative expression elements would
be undifferentiated from their expression element
counterparts
Could use existing 075 field to differentiate work and
expression authority records, hence make it clear
whether 3XX field is for work or expression element
(subject to new $2 source code)
Expression level data : MARC 21 authority and
bibliographic formats
64. Representative Expression Elements :
New content designation options
Content designation options (indicator / subfield level)
New indicators added to existing 3XX fields in authority format
(e.g. language of representative expression)
New indicators added to existing 0XX / 2XX / 3XX / 5XX fields in
bibliographic format
OR
New subfields added to existing 3XX fields in authority format
New subfields added to existing 0XX / 2XX / 3XX / 5XX fields in
bibliographic format
Content designation options (field level):
New 3XX fields in authority format (e.g. language of
representative expression)
65. Representative Expression Elements :
Option 1 (Indicator)
Sample Work Record :
Creator of work: Charles Dickens
Preferred title of work: Great expectations
Language of representative expression: English
MARC 21 Authority Record :
100 1# $a Dickens, Charles, $d 1812-1870. $t Great expectations
377 1# $a eng
New 377 1st indicator specifies that subfield $a contains code for
language of representative expression.
66. Representative Expression Elements :
Option 2 (Subfield)
Sample Work Expression Record :
Creator of work: Charles Dickens
Preferred title of work: Great expectations
Language of representative expression: English
MARC 21 Authority Record :
100 1# $a Dickens, Charles, $d 1812-1870. $t Great expectations
377 ## $x eng
New 377 $x specifies that subfield contains code for language of
representative expression.
67. Representative Expression Elements :
Option 3 (Field)
Sample Work Record :
Creator of work: Charles Dickens
Preferred title of work: Great expectations
Language of representative expression: English
MARC 21 Authority Record :
100 1# $a Dickens, Charles, $d 1812-1870. $t Great expectations
317 ## $a eng
New 317 tag specifies that field contains code for language of
representative expression.
68. Representative Expression Elements: MARC
21 Indicator / Subfield Change Candidates (1)
RDA Element MARC
Authority
MARC
Bibliographic
Aspect ratio of representative
expression
500
Colour content of representative
expression
300, 340
Content type of representative
expression
336 336
Date of capture of representative
expression
388 033/518
Duration of representative
expression
306
69. Representative Expression Elements : MARC
21 Indicator / Subfield Change Candidates (2)
RDA Element MARC
Authority
MARC
Bibliographic
Extent of representative expression 300
Intended audience of representative
expression
385 385
Key of representative expression 384 384
Language of representative
expression
377 377
Medium of performance of
representative expression
382 382
70. Representative Expression Elements: MARC
21 Indicator / Subfield Change Candidates (3)
RDA Element MARC
Authority
MARC
Bibliographic
Place of capture of representative
expression
370 033/518
Projection of cartographic content
of representative expression
255
Scale of representative expression 255
Script of representative expression 546, $6
Sound content of representative
expression
300
71. Representative Expression Elements :
Utility / Feasibility of Changes
New content designation would allow using fields for
representative expression elements in work authority
records without using 075 to indicate the type of entity.
Accommodating changes in authority format:
advantage that more content designation is still available than in
the bibliographic format.
Accommodating changes in bibliographic format :
advantage that all pre-existing expression elements are
already defined there.
72. Data provenance : Guidance
Data provenance provides information about the
metadata recorded in an element or set of elements. This
information can be used to infer the context and quality of
the metadata.
The metadata being described by data provenance are
treated as a metadata work that consists of a metadata
statement or a metadata description set.
A metadata work may be described using any
appropriate RDA elements and recording methods.
73. Data Provenance : Common Requirements
Recording an agent who publishes metadata
Recording an agent who records metadata
Recording a content standard used for metadata
Recording a language of description
Recording a scope for validity of metadata
Recording a script of description
Recording a source of metadata
Recording a timespan for validity of metadata
Recording a timespan when metadata are published
Recording a transcription standard used for metadata
74. Data Provenance : Example (1)
Sample Data Provenance (Description):
Timespan metadata published: February 23, 1994, 15:10:47
Agent who publishes metadata: British Library
Language of description: English
Agent who records metadata: British Library
Content standard used for metadata: RDA
MARC 21 Authority / Bibliographic Record:
005 19940223151047.0
040 ## $a Uk $b eng $c Uk $e rda
75. Data Provenance : Example (2)
Sample Data Provenance (Description):
Source of metadata: The Swedish phosphate report / R. Wilson,
1995, title page
MARC 21 Authority Record :
670 ## $a The Swedish phosphate report, 1995: $b title page (R. Wilson)
76. Data Provenance : Content designation
Partial content designation in MARC 21
Content designation mainly at description level
Content designation absent from field level (excepting
cases where $5 is defined)
Content designation absent from subfield level
77. Data Provenance Coverage in MARC 21 (1)
RDA Element Record Level Field Level Subfield Level
Recording an agent
who publishes
metadata
040 $a, $d $5
Recording an agent
who records metadata
040 $a, $c, $d
Recording a content
standard used for
metadata
040 $e
Recording a language
of description
040 $b
Recording a scope for
validity of metadata
78. Data Provenance Coverage in MARC 21 (2)
RDA Element Record Level Field Level Subfield Level
Recording a script of
description
LDR/09
066
Recording a source of
metadata
670 (Authority)
500,510
(Bibliographic)
Recording a timespan for
validity of metadata
Recording a timespan
when metadata are
published
005
Recording a
transcription standard
used for metadata
79. Data Provenance :
Utility / Feasibility of Changes
New content designation to represent provenance
information would support semantic web applications.
Sufficient content designation is still available to record
data provenance information in the MARC 21 authority
and bibliographic formats at the record level
Insufficient content designation is available at the field
and subfield level in the bibliographic format.
Greater scope for content designation may be available
at field and subfield level in the authority format.
80. Diachronic Works : Guidance
A diachronic work is a work that is planned to be
embodied over time, rather than as a single “act of
publication”. This effectively means that the content of
the work changes over time, by being realized in one or
more discrete expressions that are embodied in one or
more manifestations.
The essence of a diachronic work is the plan for the
change of content.
81. Diachronic Works : Categories of “Plan”
(Successive)
Successive determinate plan: “An extension plan for a
work that is intended to be realized in multiple distinct
expressions that are embodied during a closed
timespan.” (e.g. serialized novels, reference works)
Successive indeterminate plan: “An extension plan for a
work that is intended to be realized in multiple distinct
expressions that are embodied during an open timespan”
(e.g. periodicals, newspapers)
82. Diachronic Works : Categories of “Plan”
(Integrating)
Integrating determinate plan: “An extension plan for a
work that is intended to be realized in one distinct
expression that is embodied during a closed timespan.”
(e.g. project wikis, conference websites)
Integrating indeterminate plan: “An extension plan for a
work that is intended to be realized in one distinct
expression that is embodied during an open timespan.”
(e.g. updated standards, wikis)
83. Static Works
Static plan: “An extension plan for a work intended to be
realized in one or more distinct expressions that are all
embodied simultaneously.” (e.g. novels, poems)
Not planned to be embodied over time, but rather as a
single act of publication.
84. Diachronic Works:
Content designation
No content designation present in MARC 21 formats to
record the extension plan for diachronic works.
LDR 07 (bibliographic level) denotes the type of resource
being described, but not the extension plan.
As a representation of the publisher’s intent, an extension
plan may change over time.
85. Diachronic Works :
Utility / Feasibility of Changes
Recording the extension plan for diachronic works would
allow statements to be made regarding the intended
timespan of successive and integrating works before their
actual termination dates.
Sufficient content designation is still available to record
the extension plan for diachronic and static works as a
set of coded values or controlled terms in the MARC 21
authority and bibliographic formats at record level.
86. Emerging Non-MARC Data Formats:
Is Changing MARC 21 Necessary?
MARC standard now over 50 years old
Limited scope for additional content designation
Bibframe, Schema.org, etc. offer extensible schema
which could accommodate 3R changes
To what extent could / will Bibframe implement LRM?
87. 3R Project Timeline
New RDA Toolkit still in beta phase
Transition to live version not expected until 2019
Old Toolkit to be decommissioned 12 months after new
version goes live
1-2 Full MAC cycles to amend MARC
What should be the priorities?
Who will do it?
88. Implementation of Changes: Options for
Collaboration
Re-convene RDA/MARC Working Group?
http://www.rda-jsc.org/archivedsite/rdamarcwg.html
New PCC Task Group?
https://www.loc.gov/aba/pcc/taskgroup/task-groups.htm
Other?
89. Thank You
Thurstan Young
thurstan.young@bl.uk
James Hennelly
jhennelly@rdatoolkit.org
Gordon Dunsire
gordon@gordondunsire.com