mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2024-11-22 14:45:03 +01:00
Update CGSpace CG Core v2 migration notes
We will be keeping cg.identifier.dataurl instead of cg.hasMetadata.
This commit is contained in:
parent
72996d3c7c
commit
93bbddcfc6
@ -20,7 +20,7 @@ With reference to [CG Core v2 draft standard](https://agriculturalsemantics.gith
|
||||
- [Implementation Progress](#implementation-progress)
|
||||
|
||||
## Proposed Changes
|
||||
As of 2019-10-29 the scope of the changes includes the following fields:
|
||||
As of 2019-11-17 the scope of the changes includes the following fields:
|
||||
|
||||
- cg.creator.id→cg.creator.identifier
|
||||
- ORCID identifiers
|
||||
@ -50,7 +50,6 @@ As of 2019-10-29 the scope of the changes includes the following fields:
|
||||
- dc.type→dcterms.type
|
||||
- dc.identifier.isbn→cg.isbn
|
||||
- dc.identifier.issn→cg.issn
|
||||
- cg.identifier.dataurl→cg.hasMetadata
|
||||
|
||||
The following fields are currently out of the scope of this migration because they are used internally by DSpace 5.x/6.x and would be difficult to change without significant modifications to the core of the code:
|
||||
|
||||
@ -72,7 +71,6 @@ Make sure the following fields exist:
|
||||
- [x] cg.journal (246)
|
||||
- [x] cg.isbn (247)
|
||||
- [x] cg.issn (248)
|
||||
- [x] cg.hasMetadata (249)
|
||||
|
||||
## Fields to delete
|
||||
Fields to delete after migration:
|
||||
@ -81,7 +79,6 @@ Fields to delete after migration:
|
||||
- [ ] cg.fulltextstatus
|
||||
- [ ] cg.identifier.status
|
||||
- [ ] cg.link.reference
|
||||
- [ ] cg.identifier.dataurl
|
||||
|
||||
## Implementation Progress
|
||||
Tally of the status of the implementation of the new fields in the CGSpace `5_x-cgcorev2` branch.
|
||||
@ -108,7 +105,6 @@ dcterms.subject | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
|
||||
dcterms.type | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
|
||||
cg.isbn | ✓ | ✓ | - | - | - | ✓ | |
|
||||
cg.issn | ✓ | ✓ | - | - | - | ✓ | |
|
||||
cg.hasMetadata | ✓ | ✓ | ✓ | - | ✓ | ✓ | |
|
||||
|
||||
There are a few things that I need to check once I get a deployment of this code up and running:
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user