Resource and Metadata Management with a Linked Data perspective

•

0 likes•636 views

This document summarizes a presentation on resource and metadata management from a linked data perspective. It discusses projects like Organic.Edunet that deal with heterogeneous metadata from multiple standards and stakeholders. It also outlines the conceptual overview of the EntryStore system for managing linked data, including named graphs, REST API, ACLs, harvesting, querying, and SPARQL. Some lessons learned are around ontologies being difficult for annotators to grasp, the need for clear licensing of data versus metadata, and the complexity involved in practical implementation at large scale.

Technology Education

Resource and Metadata Management
with a Linked Data perspective

Meetup: Linked Data in Sweden
April 17, 2012

Hannes Ebner
hebner@kth.se
hannes@metasolutions.se

Multiple projects with similar goals

• Organic.Edunet as example because of its
characteristics
- Heterogeneous metadata
- Multiple stakeholders and standards
- Ontology
- Big user base
- Used in production environments
- Not typically academic (content-centric)

EntryStore – conceptual overview

• Named graphs
• REST API
• ACL
• Harvesting
• Querying
• On-the-fly MD conversions
• SPARQL
• Literal indexing

Open Source

Interoperability

FAO Organic
EPrints
Custom
XML
Intute
Bio@gro DC/RDF
DC/RDF

YouTube
LOM/XML
Custom

EntryStore
HTTP SPARQL

RDF core
Solr OAI-PMH
SQI

Lessons learned - ontology

• Ontology
- Good for domain experts
- Pain for “annotators”
- Nobody used ontology tree
• Flat list with type-ahead is popular
• Difficult to grasp hierarchy

Lessons learned - licensing

• Ensure licensing is clear
- Creative Commons
- Open Data Commons
- Custom licenses
- Organic.Edunet: CC0

• Data != Metadata
- Often confused when it comes to licensing

Lessons learned - interoperability

• W3C standards everywhere
- Exception: some formats, e.g. IEEE LOM

• Triplification has to be done by experts

• Remix of various vocabularies

• Search engines find resources directly

Lessons learned – practical problems

• Complexity
- Try to find a student...
- Big technology stack

• Need for authoritative and quality-controlled
(meta)data

• Legacy data has to be converted and mapped

• Scalability

WIN!

No user ever noticed the technology behind

“Rule number 1 in building web software: never show
the URI. If the URI does not have a label, go and beat
somebody up.”

Tim Berners-Lee at LDOW
April 16, 2012

FAIL?

OK, there was the ontology...

“The one big ontology approach didn't work”

Tim Berners-Lee at LDOW
April 16, 2012

Current work / experiments

• Data-driven Sustainability
- footprinted.org, in collaboration with Sourcemap.com
- Data bridges (EIT ICT Labs)
- Miljöbarometern (visualizations, Google Refine)
- Green Hackathon

• Large scale triplification and interlinking of educational metadata
- ARIADNE
- Open Discovery Space

• Contextualization of cultural heritage metadata
- Europeana (Hack4Europe!)

Resource and Metadata Management with a Linked Data perspective

What's hot

Modeling Data with Karma – Data Integration Tool

Violeta Ilik

Importing life science at a into Neo4j

Simon Jupp

Institutional Repository (IR) and Open Access in Academic Libraries

Hong (Jenny) Jing

Linking Data, Linking People

fereiraJ

Supporting Web-based Scholarly Annotation

Anna Gerber

ELIXIR-UK and the ELIXIR Interoperability Platform

ELIXIR UK

Data integration is intrinsic to how modern research is undertaken in areas such as genomics, drug development and personalised medicine. To better enable this integration a large number of biomedical ontologies have been developed to provide standard semantics for describing metadata. There are now several hundred biomedical ontologies in widespread use that describe concepts such as genes, molecules, drugs and diseases. This amounts to millions of terms that are interconnected via relationships that naturally form a graph of biomedical terminology. The Ontology Lookup Service (OLS) (http://www.ebi.ac.uk/ols) integrates over 160 ontologies and provide a central point for the biomedical community to query and visualise ontologies. OLS also provide a RESTful API over the ontologies that is used in high-throughput data annotation pipelines. OLS is built on top of a Neo4j database that provides efficient indexes for extracting ontological relationships. We have developed generic tools for loading RDF/OWL ontologies into Neo4j where the indexes are optimised for serving common ontology queries. We are now moving to adopt graph database more widely in applications relating to ontology mapping prediction and recommendation systems for data annotation.

Ontologies neo4j-graph-workshop-berlin

Simon Jupp

Semantics as a service at EMBL-EBI

Simon Jupp

Presented at the Leiden Bioscience Lecture, 24 November 2016, Reproducibility, Research Objects and Reality Over the past 5 years we have seen a change in expectations for the management of all the outcomes of research – that is the “assets” of data, models, codes, SOPs, workflows. The “FAIR” (Findable, Accessible, Interoperable, Reusable) Guiding Principles for scientific data management and stewardship have proved to be an effective rallying-cry. Funding agencies expect data (and increasingly software) management retention and access plans. Journals are raising their expectations of the availability of data and codes for pre- and post- publication. It all sounds very laudable and straightforward. BUT….. Reproducibility is a R* minefield, depending on whether you are testing for robustness (rerun), defence (repeat), certification (replicate), comparison (reproduce) or transferring between researchers (reuse). Different forms of "R" make different demands on the completeness, depth and portability of research. Sharing is another minefield raising concerns of credit and protection from sharp practices. In practice the exchange, reuse and reproduction of scientific experiments is dependent on bundling and exchanging the experimental methods, computational codes, data, algorithms, workflows and so on along with the narrative. These "Research Objects" are not fixed, just as research is not “finished”: the codes fork, data is updated, algorithms are revised, workflows break, service updates are released. ResearchObject.org is an effort to systematically support more portable and reproducible research exchange In this talk I will explore these issues in data-driven computational life sciences through the examples and stories from initiatives I am involved, and Leiden is involved in too including: · FAIRDOM which has built a Commons for Systems and Synthetic Biology projects, with an emphasis on standards smuggled in by stealth and efforts to affecting sharing practices using behavioural interventions · ELIXIR, the EU Research Data Infrastructure, and its efforts to exchange workflows · Bioschemas.org, an ELIXIR-NIH-Google effort to support the finding of assets.

Reproducibility, Research Objects and Reality, Leiden 2016

Carole Goble

ETDs and Open Access for Research and Development: Issues and challenges

Bhojaraju Gunjal

SHELDON is the first true hybridization of NLP machine reading and Semantic Web. It is a framework that builds upon a machine reader for extracting RDF graphs from text so that the output is compliant to Semantic Web and Linked Data patterns. It extends the current human-readable web by using Semantic Web practices and technologies in a machine-processable form. Given a sentence in any language, it provides different semantic functionalities (frame detection, topic extraction, named entity recognition, resolution and coreference, terminology extraction, sense tagging and disambiguation, taxonomy induction, semantic role labeling, type induction, sentiment analysis, citation inference, relation and event extraction) as well as nice visualization tools which make use of the JavaScript infoVis Toolkit and RelFinder, as well as a knowledge enrichment component that extends machine reading to Semantic Web data. The system can be freely used at http://wit.istc.cnr.it/stlab-tools/sheldon.

Sheldon challenge

Andrea Nuzzolese

Building a repository of biomedical ontologies with Neo4j

Simon Jupp

By establishing a digital repository on the Feinberg School of Medicine (FSM), Northwestern University, Chicago campus, we anticipate to gain ability to create, share, and preserve attractive, functional, and citable digital collections and exhibits. Galter Health Sciences Library did not have a repository as of November 2014. In just a few moths we formed a small team that was charged at looking to select the most suitable open source platform for our digital repository software. We followed the National Library of Medicine master evaluation criteria by looking at various factors that included: functionality, scalability, extensibility, interoperability, ease of deployment, system security, system, physical environment, platform support, demonstrated successful deployments, system support, strength of development community, stability of development organization, and strength of technology roadmap for the future. These factors are important for our case considering the desire to connect the digital repository with another platform that was an essential piece in the big FSM picture – VIVO. VIVO is a linked data platform that serves as a researchers’ hub and which provides the names of researchers from academic institutions along with their research output, affiliation, research overview, service, background, researcher’s identities, teaching, and much more.

Starting from scratch – building the perfect digital repository

Violeta Ilik

Building EOL species pages

Cyndy Parr

Open minted content_provision

Lucas anastasiou

IWMW 2003: Semantic Web Technologies for UK HE and FE Institutions (Part 2)

IWMW

What's hot (16)

Modeling Data with Karma – Data Integration Tool

Importing life science at a into Neo4j

Institutional Repository (IR) and Open Access in Academic Libraries

Linking Data, Linking People

Supporting Web-based Scholarly Annotation

ELIXIR-UK and the ELIXIR Interoperability Platform

Ontologies neo4j-graph-workshop-berlin

Semantics as a service at EMBL-EBI

Reproducibility, Research Objects and Reality, Leiden 2016

ETDs and Open Access for Research and Development: Issues and challenges

Sheldon challenge

Building a repository of biomedical ontologies with Neo4j

Starting from scratch – building the perfect digital repository

Building EOL species pages

Open minted content_provision

IWMW 2003: Semantic Web Technologies for UK HE and FE Institutions (Part 2)

Viewers also liked

Slide Vision And Scope

guest4a79da

Vision And Scope Document

guest4a79da

15.project attendence managemnt system

Haseeb Nasir

Student management system

Gaurav Subham

Project report-on-student-information-management-system-php-mysql

Raj Sharma

LinkedIn SlideShare: Knowledge, Well-Presented

SlideShare

Viewers also liked (6)

Slide Vision And Scope

Vision And Scope Document

15.project attendence managemnt system

Student management system

Project report-on-student-information-management-system-php-mysql

LinkedIn SlideShare: Knowledge, Well-Presented

Similar to Resource and Metadata Management with a Linked Data perspective

Organic.Edunet Repository Tools

Hannes Ebner

Learning Object Annotation in Agricultural Learning Repositories

Hannes Ebner

Ontology and Ontology Libraries: a critical study

Debashisnaskar

Presentation FAIRsFAIR workshop (April 2020)

INRAE (MISTEA) and University of Montpellier (LIRMM)

FAIR data requires FAIR ontologies, how do we do?

INRAE (MISTEA) and University of Montpellier (LIRMM)

394 wade word2007-ssp2008

Society for Scholarly Publishing

The concept of digital library revolutionized its popularity with the development of networking technology. Digital library stores various kind of documents in digitized format that enables user smooth access to these documents at subsidized costs. In the recent past, a similar concept i.e., ontology library has gained popularity among the communities like semantic web, artificial intelligence, information science, philosophy, linguistics, and so forth.

Ontology and Ontology Libraries: a Critical Study

Debashisnaskar

Integrating an electronic lab notebook with a data repository; American Chemi...

rmacneil88

Elns and repositories, American Chemical Society, Dallas, March 2014

ResearchSpace

McNamara - learning objects

tim mcnamara

ISWC GoodRelations Tutorial Part 2

Martin Hepp

GoodRelations Tutorial Part 2

guestecacad2

Open access e repositories kelaniya workshop final

Jagath Arachchige

Building OBO Foundry ontology using semantic web tools

Melanie Courtot

Project Website: http://www.researchobject.org/ researchobjects.org is a community project that has developed an approach to describe and package up all resources used as part of an investigation as Research Objects (RO’s). RO’s - provide two main features; a manifest - a consistent way to provide a well-typed, structured description of the resources used in an investigation; and a ‘bundle’ - a mechanism for packaging up manifests with resources as a single, publishable unit. RO’s therefore carry the research context of an experiment - data, software, standard operating procedures (SOPs), models etc - and gather together the components of an experiment so that they are findable, accessible, interoperable and reproducible (FAIR). RO’s combine software and data into an aggregative data structure consisting of well described reconstructable parts. RO’s have the potential to address a number of challenges pertinent to open research including: a) supporting interoperability between infrastructures by using ROs as a primary mechanism for exchange and publication b) supporting the evolution of research objects as a living collection, enabling provenance tracking c) providing the ability to pivot research object components (data, software, models) that are not restricted to the traditional publication. Here we present work towards the development and adoption of ROs: (i) A series of specifications and conventions, using community standards, for the RO manifest and RO bundles. (ii) Implementations of Java, Python and Ruby APIs and tooling against those specifications; (iii) Examples of representations of the RO models in various languages (e.g. JSON-LD, RDF, HTML).

Research Shared: researchobject.org

Norman Morrison

From Open Access to Open Standards, (Linked) Data and Collaborations

Simeon Warner

Metadata

Dorothea Salo

Why I don't use Semantic Web technologies anymore, event if they still influe...

Gautier Poupeau

Designing and Implementing Search Solutions

Findwise

Opening up MOOCs for OER management on the Web of linked data

Gilbert Paquette

Similar to Resource and Metadata Management with a Linked Data perspective (20)

Organic.Edunet Repository Tools

Learning Object Annotation in Agricultural Learning Repositories

Ontology and Ontology Libraries: a critical study

Presentation FAIRsFAIR workshop (April 2020)

FAIR data requires FAIR ontologies, how do we do?

394 wade word2007-ssp2008

Ontology and Ontology Libraries: a Critical Study

Integrating an electronic lab notebook with a data repository; American Chemi...

Elns and repositories, American Chemical Society, Dallas, March 2014

McNamara - learning objects

ISWC GoodRelations Tutorial Part 2

GoodRelations Tutorial Part 2

Open access e repositories kelaniya workshop final

Building OBO Foundry ontology using semantic web tools

Research Shared: researchobject.org

From Open Access to Open Standards, (Linked) Data and Collaborations

Metadata

Why I don't use Semantic Web technologies anymore, event if they still influe...

Designing and Implementing Search Solutions

Opening up MOOCs for OER management on the Web of linked data

Recently uploaded

Six Myths about Ontologies: The Basics of Formal Ontology

johnbeverley2021

In this keynote, Asanka Abeysinghe, CTO,WSO2 will explore the shift towards platformless technology ecosystems and their importance in driving digital adaptability and innovation. We will discuss strategies for leveraging decentralized architectures and integrating diverse technologies, with a focus on building resilient, flexible, and future-ready IT infrastructures. We will also highlight WSO2's roadmap, emphasizing our commitment to supporting this transformative journey with our evolving product suite.

Platformless Horizons for Digital Adaptability

WSO2

Architecting Cloud Native Applications

WSO2

"I see eyes in my soup": How Delivery Hero implemented the safety system for ...

Zilliz

CNIC Information System with Pakdata Cf In Pakistan

danishmna97

Vector Search -An Introduction in Oracle Database 23ai.pptx

Remote DBA Services

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Edi Saputra

Understanding the FAA Part 107 License ..

Christopher Logan Kennedy

Following the popularity of “Cloud Revolution: Exploring the New Wave of Serverless Spatial Data,” we’re thrilled to announce this much-anticipated encore webinar. In this sequel, we’ll dive deeper into the Cloud-Native realm by uncovering practical applications and FME support for these new formats, including COGs, COPC, FlatGeoBuf, GeoParquet, STAC, and ZARR. Building on the foundation laid by industry leaders Michelle Roby of Radiant Earth and Chris Holmes of Planet in the first webinar, this second part offers an in-depth look at the real-world application and behind-the-scenes dynamics of these cutting-edge formats. We will spotlight specific use-cases and workflows, showcasing their efficiency and relevance in practical scenarios. Discover the vast possibilities each format holds, highlighted through detailed discussions and demonstrations. Our expert speakers will dissect the key aspects and provide critical takeaways for effective use, ensuring attendees leave with a thorough understanding of how to apply these formats in their own projects. Elevate your understanding of how FME supports these cutting-edge technologies, enhancing your ability to manage, share, and analyze spatial data. Whether you’re building on knowledge from our initial session or are new to the serverless spatial data landscape, this webinar is your gateway to mastering cloud-native formats in your workflows.

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Safe Software

How to Troubleshoot Apps for the Modern Connected Worker

ThousandEyes

Dubai, known for its towering skyscrapers, luxurious lifestyle, and relentless pursuit of innovation, often finds itself in the global spotlight. However, amidst the glitz and glamour, the emirate faces its own set of challenges, including the occasional threat of flooding. In recent years, Dubai has experienced sporadic but significant floods, disrupting normalcy and posing unique challenges to its infrastructure. Among the critical nodes in this bustling metropolis is the Dubai International Airport, a vital hub connecting the world. This article delves into the intersection of Dubai flood events and the resilience demonstrated by the Dubai International Airport in the face of such challenges.

Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf

Orbitshub

Artificial Intelligence Chap.5 : Uncertainty

Khushali Kathiriya

Retrieval augmented generation (RAG) is the most popular style of large language model application to emerge from 2023. The most basic style of RAG works by vectorizing your data and injecting it into a vector database like Milvus for retrieval to augment the text output generated by an LLM. This is just the beginning. One of the ways that we can extend RAG, and extend AI, is through multilingual use cases. Typical RAG is done in English using embedding models that are trained in English. In this talk, we’ll explore how RAG could work in languages other than English. We’ll explore French, Chinese, and Polish.

Introduction to Multilingual Retrieval Augmented Generation (RAG)

Zilliz

The Good, the Bad and the Governed - Why is governance a dirty word? David O'Neill, Chief Operating Officer - APIContext Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...

apidays

Keynote 2: APIs in 2030: The Risk of Technological Sleepwalk Paolo Malinverno, Growth Advisor - The Business of Technology Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...

apidays

MINDCTI Revenue Release Quarter One 2024

MIND CTI

Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows. We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases. This video focuses on the deployment of external web forms using Jotform for Bonterra Impact Management. This solution can be customized to your organization’s needs and deployed to support the common use cases below: - Intake and consent - Assessments - Surveys - Applications - Program registration Interested in deploying web form automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.

Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...

Jeffrey Haguewood

AWS Community Day CPH - Three problems of Terraform

Andrey Devyatkin

Join our latest Connector Corner webinar to discover how UiPath Integration Service revolutionizes API-centric automation in a 'Quote to Cash' process—and how that automation empowers businesses to accelerate revenue generation. A comprehensive demo will explore connecting systems, GenAI, and people, through powerful pre-built connectors designed to speed process cycle times. Speakers: James Dickson, Senior Software Engineer Charlie Greenberg, Host, Product Marketing Manager

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

DianaGray10

When you’re building (micro)services, you have lots of framework options. Spring Boot is no doubt a popular choice. But there’s more! Take Quarkus, a framework that’s considered the rising star for Kubernetes-native Java. It always depends on what's best for your situation, but how to choose the best solution if you're comparing 2 frameworks? Both Spring Boot and Quarkus have their positives and negatives. Let us compare the two by live coding a couple of common use cases in Spring Boot and Quarkus. After this talk, you’ll be ready to get started with Quarkus yourself, and know when to select Quarkus or Spring Boot.

Spring Boot vs Quarkus the ultimate battle - DevoxxUK

Jago de Vreede

Recently uploaded (20)

Six Myths about Ontologies: The Basics of Formal Ontology

Platformless Horizons for Digital Adaptability

Architecting Cloud Native Applications

"I see eyes in my soup": How Delivery Hero implemented the safety system for ...

CNIC Information System with Pakdata Cf In Pakistan

Vector Search -An Introduction in Oracle Database 23ai.pptx

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving

Understanding the FAA Part 107 License ..

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

How to Troubleshoot Apps for the Modern Connected Worker

Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf

Artificial Intelligence Chap.5 : Uncertainty

Introduction to Multilingual Retrieval Augmented Generation (RAG)

Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...

Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...

MINDCTI Revenue Release Quarter One 2024

Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...

AWS Community Day CPH - Three problems of Terraform

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

Spring Boot vs Quarkus the ultimate battle - DevoxxUK

Resource and Metadata Management with a Linked Data perspective

1. Resource and Metadata Management with a Linked Data perspective Meetup: Linked Data in Sweden April 17, 2012 Hannes Ebner hebner@kth.se hannes@metasolutions.se

2. Multiple projects with similar goals • Organic.Edunet as example because of its characteristics - Heterogeneous metadata - Multiple stakeholders and standards - Ontology - Big user base - Used in production environments - Not typically academic (content-centric)

5. EntryStore – conceptual overview • Named graphs • REST API • ACL • Harvesting • Querying • On-the-fly MD conversions • SPARQL • Literal indexing Open Source

6. Interoperability FAO Organic EPrints Custom XML Intute Bio@gro DC/RDF DC/RDF YouTube LOM/XML Custom EntryStore HTTP SPARQL RDF core Solr OAI-PMH SQI

7. Lessons learned - ontology • Ontology - Good for domain experts - Pain for “annotators” - Nobody used ontology tree • Flat list with type-ahead is popular • Difficult to grasp hierarchy

8. Lessons learned - licensing • Ensure licensing is clear - Creative Commons - Open Data Commons - Custom licenses - Organic.Edunet: CC0 • Data != Metadata - Often confused when it comes to licensing

9. Lessons learned - interoperability • W3C standards everywhere - Exception: some formats, e.g. IEEE LOM • Triplification has to be done by experts • Remix of various vocabularies • Search engines find resources directly

10. Lessons learned – practical problems • Complexity - Try to find a student... - Big technology stack • Need for authoritative and quality-controlled (meta)data • Legacy data has to be converted and mapped • Scalability

11. WIN! No user ever noticed the technology behind “Rule number 1 in building web software: never show the URI. If the URI does not have a label, go and beat somebody up.” Tim Berners-Lee at LDOW April 16, 2012

12. FAIL? OK, there was the ontology... “The one big ontology approach didn't work” Tim Berners-Lee at LDOW April 16, 2012

13. Current work / experiments • Data-driven Sustainability - footprinted.org, in collaboration with Sourcemap.com - Data bridges (EIT ICT Labs) - Miljöbarometern (visualizations, Google Refine) - Green Hackathon • Large scale triplification and interlinking of educational metadata - ARIADNE - Open Discovery Space • Contextualization of cultural heritage metadata - Europeana (Hack4Europe!)

Resource and Metadata Management with a Linked Data perspective

Recommended

Recommended

More Related Content

What's hot

What's hot (16)

Viewers also liked

Viewers also liked (6)

Similar to Resource and Metadata Management with a Linked Data perspective

Similar to Resource and Metadata Management with a Linked Data perspective (20)

More from Hannes Ebner

More from Hannes Ebner (9)

Recently uploaded

Recently uploaded (20)

Resource and Metadata Management with a Linked Data perspective