task #6944
closedScheme for persistent name identifiers
100%
Description
As stated in #6592 we might need a persistent name identifier.
TODO:
- Discuss if a persistent name identifier is needed?
- Defined the identifier schema
Related issues
Updated by Andreas Kohlbecker over 6 years ago
we could reuse the phycobankID as identifier for name by appending /name to it:
http://phycobank.org/1298390/name
Updated by Wolf-Henning Kusber over 6 years ago
reuse of the ID is a good idea.
What about additional PhycoBankIDnumber/type if it is just a later typification?
Updated by Andreas Kohlbecker over 6 years ago
Andreas Kohlbecker wrote:
we could reuse the phycobankID as identifier for name by appending
/nameto it:http://phycobank.org/1298390/name
Reusing the localId of the phycobankID could be less robust since the local id comes from a Registration which is associated with the name by a toMany association: TaxonName 1------>n Registration (re-)constructing the persistent identifier from the localID is impossible if more than one Registrations exist for the same name.
The appendix /name seems to indicate a property. This is seems also not optimal.
Better schemes for a name identifier would be:
http://phycobank.org/name/89980340 http://name.phycobank.org/89980340
Updated by Andreas Kohlbecker over 6 years ago
- Related to task #6610: The according pyhcobcankID should be used as nameInSourceID for each name registered added
Updated by Andreas Kohlbecker almost 5 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
completed