PID Creation
- Store PID Kernel Information in Local Handle Service.
- Utilize Data Type Registry (DTR), endorsed by RDA, to store the profile of PID Kernel Information.
- Utilize PIT API, endorsed by RDA, as an SDK of tools for clients to interact with PID infrastructure.
-
The Handle system allows for inclusion of a small amount of information to be stored at the local handle server. We are exploiting this in an RDA PID Kernel Information WG to define what we call PID kernel information.
-
PID Kernel Information, if defined wisely, can enable an entirely new ecosystem of data services operating at Internet speeds.
- RPID testbed assigns only test temporary handles.
- All handles assigned by testbed are of type:
- 11723.1.test, 11723.2.test, ... 11723.8.test : assigned for internal use
- 11723.9.test. : assigned to projects
- Defined by a profile stored to the Data Type Registry.
- Pointer to the type of the data object.
- Pointer to the data object.
Kernel Information uses the Strawman profile as inside metadata. It describing PID with human-readable information. Some sample important Kernel information detail display in the table below.
| Property Identifier | Content Format | Mandatory? | Explanation | |
| 1 | PID | Handle | Yes | Global identifier for the object; external to the PID Kernel information |
| 2 | RDAKIProfileType | Handle | Yes | Handle to the Kernel Information type profile; serves as pointer to profile in DTR. Address of DTR federation expected to be global (common) knowledge. |
| 3 | digitalObjectType | Handle | Yes | Handle points to type in DTR. The type of the object (this should always be the same for this type of data, but would distinguish t from other data types) Distinguishing metadata from data objects is a client decision within a particular usage context, which may to some extent rely on the digitalObjectType value provided. |
| 4 | digitalObjectLocation | URL | Yes | Pointer to the content object location(pointer to DO) |
- Persistent Identifiers (PIDs) are globally unique IDs with a strong governance structure around them to ensure resolving authority. Our work uses the Handle System for PIDs.
- The Handle allows for a small amount of extensible defining metadata (that we call PID kernel information). This information, defined wisely, can enable an entirely new ecosystem of data services operating at Internet speeds.
- PID assigned with a global unique id with minimal metadata information.
First the RO is assign a PID that we call the Root PID.
- The (a) part shows the unique PID in the handle value. Each object in Handle system would have a unique ID for identifying. While using this Handle URL in http://hdl.handle.net, and choosing Don’t redirect to URLs, you would see the content (PID Kernel Information) of the PID.
- Part (b) is a pair of URL type with link of the JSON metadata. This JSON file is saved in Blob repository of Azure, presenting the metadata of the folder of daily device data.
- Part (c) is our own defined DTR data type, RDA Strawman. The Strawman contains the seven non-provenance fields, describing minimal information about the folder and the root PID.
- Part (d) is the matched information with the part (c).
The most important part in PID Kernel Information (PID) is part (d). Users could find the further information by browsing the digitalObjectLocation URL (the same URL link in part (b)). When the user click on the digitalObjectLocation, he would download a JSON file "fcfb91dc-5c39-406d-ade2-ac1e470f797f.json" into local machine. The sample json file format is below.
The internal files are assigned Child PIDs.
- The URL link in Child PID is referencing to the raw data file of one device.
- Child PIDs are stored to a single ORE map file that is associated with the parent (RO).
- The parent maintains rich metadata about the RO; the children have only PID Kernel Information about them.
