Showing posts with label repository. Show all posts
Showing posts with label repository. Show all posts

2020-06-11

A brief introduction of Dryad in 10 minutes

Update information (2020-10-15): 

  •  the Data package DOI + Version numbers are retiring 
  •  the Data Paper in PDF file & OAI-PMH (DSpace) are retiring, replaced by API (https://datadryad.org/api/v2/docs/) ,
  • the schema.org embedded metadata ( HTML landing page /JSON-LD), and DataCite metadata export. 

Acknowledgements:

We thank Daniella Lowenberg, Dryad Product Manager, University of California Curation Center (UC3) for useful clarifications and comments.

Andrea Wei-Ching Huang. (2020). The Story of Research Data Repository (RDR) (Version 2020-10-15T08:08:30.049287) [Data set]. Retrieved from https://data.depositar.io/dataset/rdr-story
 
resource: https://data.depositar.io/dataset/rdr-story/resource/266a3d4e-217d-408f-ada3-14e540efaea5

 

2018-10-27

Revisit: Reuse of Structured Data: Semantics, Linkage, and Realization (2)




(continue from part I) / Library and Information Science, 43.1 (2017): 7-46. / [[中文]]


RESEARCH HIGHLIGHTS: 

# An old record is not a data but now defined as a new semantic dataset. 
i.e. its triples, graphs, links, file formats ...
i.e. its revised, vocabulary encoded versions ...
ex. data:d2148340 a dcat:dataset.
#files:json-ld, ttl, XML

#
A new method to curate, publish & visualize LOD graphs via CKAN portal.
i.e. two models for one dataset published in two views.
ex. data:d2148340 a dcat:dataset. # Dublin Core @schema1
ex. data:d2148340 a data:Refined. # more semantics@schema2

#
Validation & Reproducibility: Provenance and Contexts are in details.

Practices

Example: data:d2148340 (click to enlarge)
We then make use of structured records (XML files) from a digital archive catalogue, and convert the records into semantically rich and interlinked resources on the Web. This is realized as a unified Linked Data catalogue to several digital archive collections. Our work results in a LOD catalogue (data.odw.tw) available to the public at the website . The following five parts are involved in realizing this website. 


A catalogue record, about a species of Pleione Formosana (data:d2148340), is used throughout in the paper as an example to demonstrate the way we model, convert, and represent the semantics of a structured record.

R4R Ontology (click to enlarge)
Part 1: Exploring data reuse relations in a shared context -- We review our previous research about the Relation for Reuse Ontology (R4R). In particular, we provide mechanisms for reusing article, data, and code with some flexibility of encoding provenance and license information.

Part 2: Comparing two different data conversion approaches to providing LOD for an archive catalogue -- We show two different scenarios: (1) The LOD catalogue is converted directly from a relational database, and (2) the LOD catalogue is generated from a series of format conversions --- from XML to CSV, and then to RDF. 

KB links Example (click to enlarge)
Part 3: Data profiling, cleaning and mapping -- We demonstrate format conversion processes, and we discuss the pros and cons of various ways in handling broken links in source datasets. In addition, we mapped and linked catalogue records to three external knowledge bases: GeoNames, Wikidata, and Encyclopedia of Life.  

Part 4: Using CKAN as a Linked Data platform -- We briefly introduce CKAN, an open source web-based data portal software package for curating and publishing datasets. CKAN provides data preview, search, and discovery, especially with regard to geospatial datasets. We built several extensions to CKAN in order to deposit, publish, browse, and search Linked Data. Various Linked Data representations of a catalogue record --- Turtle, RDF/XML, and JSON-LD --- can all be downloaded and reused.

Part 5: Designing an ontology for data representation and reuse -- We design an ontology voc4odw which includes the following 3 modules:

(1) The Core Model. It is comprise of a data model and a conceptual model. 




The data model represents key data structure and relation. It is a framework to illustrate data source,derivation, and provenance.

The voc4odw Data Model (click)
The conceptual model incorporates Simple Knowledge Organization System (SKOS); it also connects to key event concepts. The conceptual model allows for data contextualization using common and domain knowledge vocabularies.



(2) The Curation Model. It is responsible for disclosing the identification, classification, and publication of structured records at a curation platform, such as the classification of themes, the assignment of data identifiers, and the publication of datasets.

(3) A vocabulary voaf:Vocabulary. It is defined as "A vocabulary used in the Linked Data cloud", from the Vocabulary of a Friend . This module is to relate the Core Model to external common vocabularies. Some hierarchy relations between different external vocabularies can be traced with this vocabulary.


voc4odw ontology
Common Knowledge
Prefix
Namespace
Description
cc
http://creativecommons.org/ns#
csvw
http://www.w3.org/ns/csvw#           
dc
dcat
dct
5.       DCMI Metadata Terms
dctype
http://purl.org/dc/dcmitype/
6.       DCMI Type Vocabulary
event
http://purl.org/NET/c4dm/event.owl#
7.       Event Ontology
foaf
geo
http://www.w3.org/2003/01/geo/wgs84_pos#
gn
10.     GeoNames Ontology
gns
11.     GeoNames Entity
lcsh
http://id.loc.gov/authorities/subjects
org
prov
r4r
schema
16.     Schema.org
skos
time
http://www.w3.org/2006/time#
18.     W3C  Time Ontology
voaf
http://purl.org/vocommons/voaf#
wde
http://www.wikidata.org/entity/
20.     Wikidata Entity
 Domain Knowledge
aat
http://vocab.getty.edu/aat/
dwc
2.       Darwin Core Terms
dwciri
3.       Darwin Core terms
eol
4.       The Encyclopaedia of Life (EOL)
txn
http://lod.taxonconcept.org/ontology/txn.owl#
Local Namespace
voc
http://voc.odw.tw/ontology#  
agent
article
code
data
5.      Linked Data for ODWeb
evt84
6.      Event Entity in ODW
project
7.      Project Entity in ODW
r1 (n)
http://data.odw.tw/r1/   (r2, r3…)
refined
http://data.odw.tw/refined/
catdat
http://catalog.digitalarchives.tw/

2016-10-04

LOD can be hugged by human: data.odw.tw.





LODs are nowadays all in love with machines (try 614 examples represented with 3 event types: schema:CreateAction, schema:OrganizeAction, and schema:PublicationEvent.)  Yet it can be hugged by human through CKAN at data.odw.tw
This is the Prat II of the Story of One Leaf, an implementation of the R4R ontology for reusing digital objects for 843312 reused objectsFor instance, see the leaf Pleione formosana Hayata (台灣一葉蘭) in the reusing context.


The Story of One Leaf/ D Version Examples: data:d2148340 (Pleione formosana Hayata 台灣一葉蘭)
data:d2148340 a data:Reused, r4r:RRObject, dcat:Dataset ;
r4r:hasProvenance data:p20160530-d2148340 ;
dc:publisher "中央研究院生物多樣性研究中心"^^rdf:PlainLiteral ;
dc:source "台灣本土植物資料庫
(http://taiwanflora.sinica.edu.tw/)"^^rdf:PlainLiteral ;
dc:date "採集日期:1993-04-25"^^rdf:PlainLiteral ;
dc:coverage "國家:台灣"^^rdf:PlainLiteral,
"最低海拔:1650"^^rdf:PlainLiteral,
"行政區:宜蘭縣大同鄉"^^rdf:PlainLiteral .
  • The case data:d2148340 in details is a data:Reused resource, a basic data component in the current Linked Data in the Open Data Web. It uses the R4R ontology to declare its URI as http://data.odw.tw/record/d2148340, and thus it can be shared later with its refined semantic versions using the same URI (ex. its R1 Version). It has provenance information using r4r:hasProvenance to relate the r4r:RRObject with its provenance information.
  • The data:Reused resource is a dcat:Dataset which is a collection of triples, published and curated by ODW, and available for access or download in many versions and formats.
  • Currently, the data:Reused resources are described with Dublin Core 15 Elements (DC15) in close relation to  their primary data. Here we call them DC 15 Version or D Version. Further semantic refinement is done by the refined versions, defined as data:Refined (we call them R Version, with different R1, R2, R3...) extracting information from the values of DC 15 properties. 



    See the leaf  in a semantically refined context:






The Story of One Leaf/ R Version Examples: data:d2148340 (Pleione formosana Hayata 台灣一葉蘭)
data:d2148340 a data:Refined, r4r:Data, dcat:Dataset ;
r4r:hasProvenance data:p20160706-d2148340 ;
txn:hasEOLPage eol:1134120;
dct:requires evt84:event-d2148340, evt84:phyCre-d2148340 ;
dcat:landingPage r1:r1-r2148340;
dcat:themeTaxonomy data:Biology .
evt84:phyCre-d2148340 a schema:CreateAction ;
event:factor dct:PhysicalResource ;
event:product dwc:PreservedSpecimen ;
dwc:eventDate "1993-04-25" ;
skos:inScheme dwc:HumanObservation ;
skos:scopeNote "specimen collection process" .
  • The data:d2148340 is a data:Reused, but also a data:Refined in different contexts. It is a semantically refined version (a r4r:Data in the R Version) of the data:Reused (a r4r:RRObject in D Version). In other words, data:d2148340 and r1:r1-r2148340 share the same URI according to the definition of the r4r:RRObject. which conveys the relation that the r1:r1-r2148340 (a r4r:Data) is a subclass of the data:d2148340 (a r4r:Object).
  • What distinguishes D Version and R Version most ?
    (1) the former with literal values, the latter with URI resource values.
    (2) the latter heavily relies on the event model (further described by using the former that the subject  dct:requires events to denote its people-place-time relations (extracting values of dc:coverage and dc:date from the former). Ex. the event evt84:phyCre-d2148340 triples as shown in the example.
    (3) the latter based on the curation context (data:ConceptTheme, ex. data:Biology) to enrich the resource with domain knowledge like EOL pages, dwc:PreservedSpecimenl and dwc:HumanObservation.




The following slides are a general overview for data.odw.tw.




Triples of the Girl Lost in Thought for Human:

Version D: represented with DC 15 Elements and Provenance (PROV-O)
Version R(r1): represented with refined spatial temporal information and linked to Wikidata, GeoNames, AAT …)