RDA Europe: Views about PID Systems - PowerPoint Presentation

Slide1

RDA Europe: Views about PID Systems Hands-On Session on PID registration and resolution and Type Registration

Tibor KálmánGesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen (GWDG)Tibor [dot] Kalman [at] gwdg [dot] de

RDA Europe: Views about PID Systems

1

01.09.2016Slide2

OverviewMotivationSimple Usage Examples

(webbrowser + curl)Resolution, CreateAdvanced Usage Examples (curl)CreateMetadata Search (URL, checksum, fields)Using existing identifiers

Template HandlesInfoType RegistryInfrastructure

PID ReplicationPID ‘interoperation’

2 von ??

RDA Europe: Views about PID Systems

01.09.2016Slide3

Motivation3

von ??RDA Europe: Views about PID Systems 01.09.2016Slide4

MotivationThis session is

intended to show some basic and advanced usage examples of Handle persistent identifiers (PIDs) hosted

by ePIC

. It helps to

understand how PIDs can be

resolved

and

maintaned

.

The

tutorial

uses

the following services:PID resolution: the Handle Proxy server for generic PID resolutionPID management: the Demo PID service of GWDG and the ePIC-API-version2

01.09.2016

RDA Europe: Views about PID Systems

4Slide5

Hands-On Session:ePIC FAQ: http://www.pidconsortium.eu/?page_id=

1060ePIC Policy & QoS: http://www.pidconsortium.eu/?page_id=904ePIC API docs: http://docs.pidconsortium.eu/

The following Handle PID

examples can be

used for testing:21.T11998/4B7335BF-CA0C-4671-9AAF-F36AE8AC88AB

21.T11998/TEMPLATEHANDLE

10.1000/182

11148/0000-0003-0B00-1

10.5072/11148/0000-0003-0B00-

1

ePIC

PID Service (DEMO):

http://demo.pidconsortium.eu/handles/

21.

T

11998/

User: rdademo1

Passwd: Training201601.09.2016RDA Europe: Views about PID Systems 5Slide6

Simple Usage Examples

01.09.2016RDA Europe: Views about PID Systems 6 von ??Slide7

Resolution 01.09.2016

RDA Europe: Views about PID Systems 7Slide8

Resolution (1)Use the Handle Proxy

server to resolve the example PIDs aboveUse the online form at the web page of

the Handle Proxy.

Use the Handle

Proxy to directly resolve

a PID

without

the

form (PID

is

part

of

the URL).Use the Handle Proxy server to get the metadata of the example PIDs above. (Hint: look at the documentation of the proxy)

Handle Proxy: http://hdl.handle.net/

01.09.2016

RDA Europe: Views about PID Systems

8Slide9

Resolution (2)Use the ePIC

PID Service (DEMO) to resolve the example PID 21.T11998/0000-0011-2DA4-2Use a web browser to get the

metadata of

the PIDhint

: PID is part of

the

URL

Use

a (

command

line

) HTTP

client

hint

:

look

at the documentation of the ePIC-API-v2ePIC PID Service (DEMO): http://demo.pidconsortium.eu/handles/21.T11998/User: rdademo1Passwd: Training201601.09.2016RDA Europe: Views about PID Systems

9Slide10

Solutions (1)01.09.2016RDA Europe: Views about PID Systems

10Slide11

Solutions (2)

01.09.2016RDA Europe: Views about PID Systems 11Slide12

CREATE & MAINTAIN a PID01.09.2016

RDA Europe: Views about PID Systems 12Slide13

ManagementUse a REST client (e.g.

curl command line client) to manage PIDs with the ePIC PID Service Create a PID with your

test user

Show

the metadata

of

your

PID

Modify

your

PID

hint

: update

the

location

(URL)ePIC PID Service (DEMO): http://demo.pidconsortium.eu/handles/21.T11998/User: rdademo1Passwd: Training201601.09.2016RDA Europe: Views about PID Systems 13Slide14

Solutions (1)01.09.2016RDA Europe: Views about PID Systems

14curl -v -

u 'rdademo1:

Training2016‘ -H "

Accept:application/json"

-

H "

Content-Type:application

/

json

"

-

X POST

-

-

data

'[{"type":"URL"

, "parsed_data":"https://rd-alliance.org/views-about-pid-systems-training-course"}]'

http://

demo.pidconsortium.eu/

handles/21.T11998

Request

Response

(Header)

Response

(Body)Slide15

Solutions (2)01.09.2016RDA Europe: Views about PID Systems

15Slide16

Advanced Usage Examples

16 von ??RDA Europe: Views about PID Systems 01.09.2016Slide17

CREATE a PID with DC5 Metadata

01.09.2016RDA Europe: Views about PID Systems 17Slide18

‘Basic‘ PID vs PID with DC5 metadata

01.09.2016RDA Europe: Views about PID Systems 18Slide19

ManagementUse a REST client (e.g.

curl command line client) to manage PIDs with the ePIC PID Service Create a PID with your

test user

Show

the

metadata

of

your

PID

ePIC

PID Service

(DEMO):

http:/

/demo.pidconsortium.eu/handles/21.T11998/User: rdademo1Passwd: Training201601.09.2016RDA Europe: Views about PID Systems 19Slide20

Solutions01.09.2016RDA Europe: Views about PID Systems

20curl

-v -u

'Rdademo1:Training2016' -H "Accept:application

/json" -H "Content-Type:application

/

json

" -X POST

-

-

data

'

[{"type":"URL"

, "

parsed_

data

":"http://ratswd.de/dl/downloads/......pdf"}, {"type":"TITLE", "parsed_data":"European Persistent Identifier Consortium - PIDs

..."}

,{"type":"AUTHORS"

, "parsed_data

":"Tibor Kálmán, Daniel Kurzawe, Ulrich

Schwardmann

"}, {"type":"PUBDATE"

, "

parsed_data":"2012"},

{

"type":"PUBLISHER","parsed_

data

":"

Scivero

"}

,

{

"type":"METADATA_URL","parsed_

data

":"http://d-

nb.info

/1030352194/

about

/

rdf

"}]'

"

http://

demo.pidconsortium.eu

/

handles

/21.T11998"Slide21

existing ID as an epic PID

01.09.2016RDA Europe: Views about PID Systems 21Slide22

Using ID ‘ABCD-1234‘

01.09.2016RDA Europe: Views about PID Systems 22curl

-v -u 'rdademo1:Training2016' -H "

Accept:application/

json" -H "Content-Type:application/

json

"

-

X

PUT

-

-

data

'[{"type":"URL","parsed_

data

":"http://

www.gwdg.de/TEST/099"}]' http://demo.pidconsortium.eu/handles/21.T11998/ABCD-1234Slide23

Metadata seaerch01.09.2016

RDA Europe: Views about PID Systems 23Slide24

Metadata SearchReverse Lookup for

an object: Checking whether the object with the exact URL http://ratswd.de/dl/downloads/langzeitarchivierung_von_forschungsdaten.pdf has already had a PID:

curl -u '

tkalman:passMyPaSsWoRd' -H "Accept:application/json

" http://pid.gwdg.de/handles/11022/?URL=http://ratswd.de/dl/downloads/langzeitarchivierung_von_forschungsdaten.pdf(Note

the

?URL=...

Parameter.)

Reverse

Lookup:

generic

search

:

Getting

the list of PIDs, where the URL contains "tibor":curl -u 'tkalman:pass‘ [...headers...] http://pid.gwdg.de/handles/11022/?URL=*tibor*(Note the ?URL=*pattern* parameter. The generic

search works

for all registered fields

. The pattern can

be an exact string or can contain

wildcards

.

Interested

readers

might

also check

the

limit

=0

parameter

in

the

"VIEW all

details

"

example

above

.)

Reverse

Lookup:

generic

search

with

more

patterns

:

Getting

the

list

of

PIDs,

where

the

AUTHORS

contains

"Tibor"

and

the

URL

contains

"

gwdg.de

"

and

the

PIDs

were

registered

by

the

institute

with

id

: 1001

:

curl

-

u

'

tkalman:pass

‘

[...

headers

...]

http

://pid.gwdg.de/handles/11022/

?AUTHORS=*tibor*&URL=*gwdg.de*&INST=1001

(Note

the

?AUTHORS=*

pattern

*

,

the

URL=*

pattern

*

and

the INST=... parameters. Interested readers might also check the limit=0 parameter in the "VIEW all details" example above.)

01.09.2016

RDA Europe: Views about PID Systems

24Slide25

Common ParametersAdditional PREFIX & SUFFIX for

the PID:curl -v -u 'rdademo1:Training2016' -H "Accept:application/json" -H "Content-Type:application/json" -X POST --data '[{"type":"URL","parsed_data":"https://rd-alliance.org/views-about

-pid-systems-training-course"}

]‘ http://demo.pidconsortium.eu/handles

/21.T11998?prefix=RDA&suffix=TRAINING

Result

: 21

.T11998/

RDA-

0000-0001-320E-8

-TRAINING

Using

generators

(

for

example, PID string is UUID):curl -v -u 'rdademo1:Training2016' -H "Accept:application/json" -H "Content-Type:application/json" -X POST --data '[{"type":"URL","parsed_data":"http://www.gwdg.de/TEST/001"}]' http://demo.pidconsortium.eu/handles/21.T11998?generator=uuidResult: 21.T11998/

2A571CF2-6FC0-11E6-96B0-E41F1343FB94

01.09.2016

RDA Europe: Views about PID Systems

25Slide26

Fragment Identifiers /Template Handles

01.09.2016RDA Europe: Views about PID Systems 26Slide27

Fragment Identifiers/Template HandlesOne

object/entity and ‘unlimited‘ number of fragments:http://www.domain.org/video?begin=10&end=20http://www.domain.org/video?begin=15&end=

25http

://www.domain.org/video?begin=100&end=200http

://www.domain.org/book1?seite=10Fragment

identifiers

/ Template

Handles

can

be

used

to

reference

an unlimited number of fragments of an object/entity without registering each potential fragment with a separate PID. utilize a 'base' and an 'extension‘the ​'template delimiter' devides the original Handle into a ​

base​ and an

extension and it

is generally defined

for the namespace (prefix)

Example

:

PID: http://

hdl.handle.net

/123-456-789@begin=10&end=20

URL: http://

www.domain.org

/

video?begin

=10&end=

20

01.09.2016

RDA Europe: Views about PID Systems

27Slide28

Fragment Identifiers/Template Handles Hands-On excercise

:Find out, which delimiter is used for templates in 21.T11998 and with which character

it is

replaced. Hint:

look for the content

of

0.NA

/21.T11998

at

the

P

roxy

Use

this

delimiter, to address a fragment together with the PID 21.T11998/TEMPLATEHANDLEHint: resolve 21.T11998/TEMPLATEHANDLE@abc=123&defghi=56789 at the Handle ProxyHandle Proxy: http://hdl.handle.net/

01.09.2016

RDA Europe: Views about PID Systems

28Slide29

Solutions (1)Standardized way

to define TemplatesExample:Prefix handle ‘0.NA/21.T11998‘‘HS_NAMESPACE‘ typeNotes (experiences and open issues)Granularity (

book, page,

etc)ReplicationePIC

: 1+2 replicasAlso the resolution

of

replica

PIDs

should

support

fragments

!

@

ePIC: this is part of the policyPID Audit is challengingMetadata for each fragment the PIDPersistency of fragment IDs

01.09.2016

RDA Europe: Views about PID Systems

29

Try

to

resolve

:

http

://

hdl.handle.net

/21.T11998/

TEMPLATEHANDLE

@abc

=123

&

defghi=

56789Slide30

ePIC PIT DTR 01.09.2016

RDA Europe: Views about PID Systems 30Slide31

ePIC PID InfoTypes RegistryePIC

PIT DTR main page: http://dtr.pidconsortium.eu/Registration of PID InfoTypes is an endorsement process

Workflow:All PITs, which

are currently

registered, are "candidates“‘Reviewers

‘

approve

PITs

A

fter PITs

become

approved

,

they

are

frozenChange in approved PITs requires a new version For the endorsement process a ‘reviewing board‘ needs to be establishedExercise:

Check the ‘

candidate‘ type: ‘date-time‘

01.09.2016

RDA Europe: Views about PID Systems 31Slide32

ePIC PIT DTR registration GUI (candidates)

01.09.2016RDA Europe: Views about PID Systems 32Slide33

ePIC PIT DTR registration GUI (candidates)01.09.2016RDA Europe: Views about PID Systems

33Slide34

PID Infrastructure01.09.2016

RDA Europe: Views about PID Systems 34Slide35

PID Replication01.09.2016

RDA Europe: Views about PID Systems 35Slide36

Replication Information in Prefix

01.09.2016RDA Europe: Views about PID Systems 36Slide37

ePIC siteinfo Tool

01.09.2016RDA Europe: Views about PID Systems 37Slide38

ePIC siteinfo(JSON)01.09.2016

RDA Europe: Views about PID Systems 38Slide39

ePIC siteinfoHigher Level Services

01.09.2016RDA Europe: Views about PID Systems 39Slide40

Thank you!Tibor Kálmán

Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen (GWDG)Tibor [dot] Kalman [at] gwdg [dot] dePID dieses Vortrages:

40 von ??

RDA Europe: Views about PID Systems

01.09.2016Slide41

Backup slides01.09.2016

RDA Europe: Views about PID Systems 41Slide42

EPIC PID vs DataCite DOIEPIC

Metadata „schema“ in EPIC GWDG v1: Dublin Core 5Metadata in EPIC v2: depends on the communityPID records are managed by

the PID-Service Metadata is

stored in the PID

DataCite

DataCite

Metadata

Schema

More

services

are

involved

in

the

management of a DOI record (incl. Metadata)Registration and management is a 2-steps processMetadata is not stored in the DOI, but in the MetaData Store21.07.14Tibor Kalman - Using DataCite DOIs in EPICSlide43

Using DOIs at EPICPolicy

for DOI „migration“:Community requirements are not clear at the momentIdea:Register EPIC PIDs by PID-Service

Maintain metadata

of the EPIC PID

Register DOI (PID metadata would be

automatically

transformed

to

DataCite

metadata

)

DOI

has the same „ID“EPIC PID: 11148/0000-0003-0B00-1DataCite DOI: 10.5072/11148/0000-0003-0B00-121.07.14Tibor Kalman - Using DataCite DOIs in EPICSlide44

Sequence Diagram (PIDDOI)

21.07.14Tibor Kalman - Using DataCite DOIs in EPICSlide45

Register an EPIC PID first

21.07.14Tibor Kalman - Using DataCite DOIs in EPICSlide46

PID-Service View of EPIC PID

21.07.14Tibor Kalman - Using DataCite DOIs in EPICSlide47

Get Metadate of the EPIC PID

21.07.14Tibor Kalman - Using DataCite DOIs in EPICSlide48

Check EPIC PID Metadata again

21.07.14Tibor Kalman - Using DataCite DOIs in EPICSlide49

Create DOI (2 Hidden Steps: MDS and DOI)

21.07.14Tibor Kalman - Using DataCite DOIs in EPICSlide50

DOI Info @ MDS

21.07.14Tibor Kalman - Using DataCite DOIs in EPICSlide51

Converted EPIC Metadata for DOI

21.07.14Tibor Kalman - Using DataCite DOIs in EPICSlide52

StatusCase study has

already been madeMetadata transformation might be challengingAll EPIC users are mapped to one

DataCite user

Authorization issues ‘ll

be handled by PID-Service

All

DataCite

registration

steps

(

Metadata

, DOI,

etc

)

are

encapsulated into one step by the PID-ServiceFault handling is challengingMore steps might be a better ideaContinue consulting with DataCiteCommunities: what are

the real requirements?

21.07.14

Tibor Kalman - Using

DataCite DOIs in EPIC