1. RDA Europe: Views about PID Systems
RDA Europe: Views about PID Systems Hands-On Session on PID registration and resolution and Type Registration
Tibor Kálmán
Gesellschaft für wissenschaftliche
Datenverarbeitung mbH Göttingen (GWDG)
Tibor [dot] Kalman [at] gwdg [dot] de
RDA Europe: Views about PID Systems

2. RDA Europe: Views about PID Systems
Overview
Motivation
Simple Usage Examples (webbrowser + curl)
Resolution, Create
Advanced Usage Examples (curl)
Create
Metadata Search (URL, checksum, fields)
Using existing identifiers
Template Handles
InfoType Registry
Infrastructure
PID Replication
PID ‘interoperation’
RDA Europe: Views about PID Systems

3. RDA Europe: Views about PID Systems
Motivation
RDA Europe: Views about PID Systems

4. Motivation
This 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 resolution
PID management: the Demo PID service of GWDG and the ePIC-API-version2
ePIC-API-v2
GWDG API v1
SURFsara API v1
Other API v1
ePIC-API-v2 (you are here)
Handle System DB
RDA Europe: Views about PID Systems

5. RDA Europe: Views about PID Systems
Hands-On Session:
ePIC FAQ:
ePIC Policy & QoS:
ePIC API docs:
The following Handle PID examples can be used for testing:
21.T11998/4B7335BF-CA0C AAF-F36AE8AC88AB
21.T11998/TEMPLATEHANDLE
/182
11148/ B00-1
/11148/ B00-1
ePIC PID Service (DEMO):
User: rdademo1
Passwd: Training2016
RDA Europe: Views about PID Systems

6. RDA Europe: Views about PID Systems
Simple Usage Examples
RDA Europe: Views about PID Systems

7. RDA Europe: Views about PID Systems
Resolution
RDA Europe: Views about PID Systems

8. RDA Europe: Views about PID Systems
Resolution (1)
Use the Handle Proxy server to resolve the example PIDs above
Use 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:
RDA Europe: Views about PID Systems

9. RDA Europe: Views about PID Systems
Resolution (2)
Use the ePIC PID Service (DEMO) to resolve the example PID 21.T11998/ DA4-2
Use a web browser to get the metadata of the PID
hint: PID is part of the URL
Use a (command line) HTTP client
hint: look at the documentation of the ePIC-API-v2
ePIC PID Service (DEMO):
User: rdademo1
Passwd: Training2016
RDA Europe: Views about PID Systems

10. RDA Europe: Views about PID Systems
Solutions (1)
RDA Europe: Views about PID Systems

11. RDA Europe: Views about PID Systems
Solutions (2)
RDA Europe: Views about PID Systems

12. RDA Europe: Views about PID Systems
CREATE & MAINTAIN a PID
RDA Europe: Views about PID Systems

13. RDA Europe: Views about PID Systems
Management
Use 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):
User: rdademo1
Passwd: Training2016
RDA Europe: Views about PID Systems

14. RDA Europe: Views about PID Systems
Solutions (1)
curl -v -u 'rdademo1:Training2016‘
-H "Accept:application/json"
-H "Content-Type:application/json"
-X POST
--data '[{"type":"URL", "parsed_data":"
Request
Response
(Header)
Response
(Body)
RDA Europe: Views about PID Systems

15. RDA Europe: Views about PID Systems
Solutions (2)
RDA Europe: Views about PID Systems

16. Advanced Usage Examples
RDA Europe: Views about PID Systems

17. CREATE a PID with DC5 Metadata
RDA Europe: Views about PID Systems

18. ‘Basic‘ PID vs PID with DC5 metadata
RDA Europe: Views about PID Systems

19. RDA Europe: Views about PID Systems
Management
Use 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):
User: rdademo1
Passwd: Training2016
RDA Europe: Views about PID Systems

20. RDA Europe: Views about PID Systems
Solutions
curl -v -u 'Rdademo1:Training2016' -H "Accept:application/json" -H "Content-Type:application/json" -X POST --data
'[{"type":"URL", "parsed_data":"
{"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":"
"
RDA Europe: Views about PID Systems

21. existing ID as an epic PID
RDA Europe: Views about PID Systems

22. RDA Europe: Views about PID Systems
Using ID ‘ABCD-1234‘
curl -v -u 'rdademo1:Training2016' -H "Accept:application/json" -H "Content-Type:application/json"
-X PUT
--data '[{"type":"URL","parsed_data":"
RDA Europe: Views about PID Systems

23. RDA Europe: Views about PID Systems
Metadata seaerch
RDA Europe: Views about PID Systems

24. RDA Europe: Views about PID Systems
Metadata Search
Reverse Lookup for an object: Checking whether the object with the exact URL has already had a PID:
curl -u 'tkalman:passMyPaSsWoRd' -H "Accept:application/json"
(Note the ?URL=... Parameter.)
Reverse Lookup: generic search: Getting the list of PIDs, where the URL contains "tibor":
curl -u 'tkalman:pass‘ [...headers...]
(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...]
(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.)
RDA Europe: Views about PID Systems

25. RDA Europe: Views about PID Systems
Common Parameters
Additional 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":"
Result: 21.T11998/RDA E-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":"
Result: 21.T11998/2A571CF2-6FC0-11E6-96B0-E41F1343FB94
RDA Europe: Views about PID Systems

26. Fragment Identifiers /Template Handles
RDA Europe: Views about PID Systems

27. Fragment Identifiers/Template Handles
One object/entity and ‘unlimited‘ number of fragments:
Fragment 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:
URL:
RDA Europe: Views about PID Systems

28. 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 Proxy
Use this delimiter, to address a fragment together with the PID
21.T11998/TEMPLATEHANDLE
Hint: resolve at the Handle Proxy
Handle Proxy:
RDA Europe: Views about PID Systems

29. RDA Europe: Views about PID Systems
Solutions (1)
Standardized way to define Templates
Example:
Prefix handle ‘0.NA/21.T11998‘
‘HS_NAMESPACE‘ type
Notes (experiences and open issues)
Granularity (book, page, etc)
Replication
ePIC: 1+2 replicas
Also the resolution of replica PIDs should support fragments!
@ePIC: this is part of the policy
PID Audit is challenging
Metadata for each fragment the PID
Persistency of fragment IDs
Try to resolve:
RDA Europe: Views about PID Systems

30. RDA Europe: Views about PID Systems
ePIC PIT DTR
RDA Europe: Views about PID Systems

31. ePIC PID InfoTypes Registry
ePIC PIT DTR
main page:
Registration of PID InfoTypes is an endorsement process
Workflow:
All PITs, which are currently registered, are "candidates“
‘Reviewers‘ approve PITs
After PITs become approved, they are frozen
Change in approved PITs requires a new version
For the endorsement process a ‘reviewing board‘ needs to be established
Exercise:
Check the ‘candidate‘ type: ‘date-time‘
RDA Europe: Views about PID Systems

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

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

34. RDA Europe: Views about PID Systems
PID Infrastructure
RDA Europe: Views about PID Systems

35. RDA Europe: Views about PID Systems
PID Replication
RDA Europe: Views about PID Systems

36. Replication Information in Prefix
RDA Europe: Views about PID Systems

37. RDA Europe: Views about PID Systems
ePIC siteinfo Tool
RDA Europe: Views about PID Systems

38. RDA Europe: Views about PID Systems
ePIC siteinfo (JSON)
RDA Europe: Views about PID Systems

39. ePIC siteinfo Higher Level Services
RDA Europe: Views about PID Systems

40. RDA Europe: Views about PID Systems
Thank you!
Tibor Kálmán
Gesellschaft für wissenschaftliche
Datenverarbeitung mbH Göttingen (GWDG)
Tibor [dot] Kalman [at] gwdg [dot] de
PID dieses Vortrages:
RDA Europe: Views about PID Systems

41. RDA Europe: Views about PID Systems
Backup slides
RDA Europe: Views about PID Systems

42. EPIC PID vs DataCite DOI
Metadata „schema“ in EPIC GWDG v1: Dublin Core 5
Metadata in EPIC v2: depends on the community
PID records are managed by the PID-Service
Metadata is stored in the PID
DataCite Metadata Schema
More services are involved in the management of a DOI record (incl. Metadata)
Registration and management is a 2-steps process
Metadata is not stored in the DOI, but in the MetaData Store
Tibor Kalman - Using DataCite DOIs in EPIC

43. Tibor Kalman - Using DataCite DOIs in EPIC
Using DOIs at EPIC
Policy for DOI „migration“:
Community requirements are not clear at the moment
Idea:
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/ B00-1
DataCite DOI: /11148/ B00-1
Tibor Kalman - Using DataCite DOIs in EPIC

44. Sequence Diagram (PIDDOI)
Tibor Kalman - Using DataCite DOIs in EPIC

45. Register an EPIC PID first
Tibor Kalman - Using DataCite DOIs in EPIC

46. PID-Service View of EPIC PID
Tibor Kalman - Using DataCite DOIs in EPIC

47. Get Metadate of the EPIC PID
Tibor Kalman - Using DataCite DOIs in EPIC

48. Check EPIC PID Metadata again
Tibor Kalman - Using DataCite DOIs in EPIC

49. Create DOI (2 Hidden Steps: MDS and DOI)
Tibor Kalman - Using DataCite DOIs in EPIC

50. Tibor Kalman - Using DataCite DOIs in EPIC
DOI MDS
Tibor Kalman - Using DataCite DOIs in EPIC

51. Converted EPIC Metadata for DOI
Tibor Kalman - Using DataCite DOIs in EPIC

52. Tibor Kalman - Using DataCite DOIs in EPIC
Status
Case study has already been made
Metadata transformation might be challenging
All 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-Service
Fault handling is challenging
More steps might be a better idea
Continue consulting with DataCite
Communities: what are the real requirements?
Tibor Kalman - Using DataCite DOIs in EPIC