-
Notifications
You must be signed in to change notification settings - Fork 5
GoKB Canonical Package Format
Ian Ibbotson edited this page Jun 2, 2016
·
3 revisions
Goal of this format
To be an expressive, canonical, reproducible, testable package exchange format. To be deterministic To support the system level needs of the electronic resource management community
Rules Contents MUST be strictly ordered by publication.title to support matching, diffing and processing Each component must have at least one unique identifier Package - Probably opaque Title - ISSN, eISSN, ISBN, DOI, ... Platform - Probably a URI, others
{
package : {
identifiers : [
{ namespace:'', value:'', checksum:'' },
]
},
contents:[
{
publication:{
type:'Journal'
title:'xxx',
identifiers:[
{ namespace:'issn', value:'1234-5678', checksum:'' },
{ namespace:'issn', value:'', checksum:'' },
{ namespace:'eissn', value:'', checksum:'' },
]
}
platform:{
}
coverage:[
{},
]
}
]
}
Identifier UUID : MD5(namespace + value + title)
- Title identifiers use publication title
- Package identifiers use package title