[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[EP-tech] Re: Versioning in EPrints 3
I suggest having a look at the way the collections plugin works. Although not exactly what you need it is a good example of using the core field 'relation' to describe a new sort of relationship between two eprints items.
The original uses 'hasPart' to denote that a collection item is made up of other items. The version at github.com/eprintsug adds a reciprocal 'isPart' to the child items. It then makes use of get_all_related etc
I'd recommend a look at this to see the mechanics of a plug in that defines a new sort of internal relationship in EPrints with the hope that it would inspire you to write your own.
Digital Archives & Research Technologies
University of London Computer Centre
t: +44 (0)20 7863 1344
e: rory.mcnicholl at london.ac.uk
The University of London is an exempt charity in England and Wales.
From: eprints-tech-bounces at ecs.soton.ac.uk <eprints-tech-bounces at ecs.soton.ac.uk> on behalf of Simukovic, Elena <elena.simukovic at wu.ac.at>
Sent: 23 June 2015 11:00:22
To: eprints-tech at ecs.soton.ac.uk
Subject: [EP-tech] Re: Versioning in EPrints 3
we were wondering if anyone else has come across this issue so far and/or has an idea for an elegant solution. We are still very interested to hear more about your experiences.
Thanks in advance,
Von: eprints-tech-bounces at ecs.soton.ac.uk [mailto:eprints-tech-bounces at ecs.soton.ac.uk] Im Auftrag von Simukovic, Elena
Gesendet: Montag, 18. Mai 2015 09:56
An: eprints-tech at ecs.soton.ac.uk
Betreff: [EP-tech] Versioning in EPrints 3
we are looking for a way to interlink different versions of an item ("version thread / tree") that are related to each other but not necessarily in a successor-predecessor relationship. A common use case example is a (working) paper or a conference/workshop item that is revised and published later as a journal article. Yet using the metadata field 'succeeds' is not appropriate in this case as both versions should be retained and not replaced; a 'commentary' by EPrint Object definition doesn't seem to apply neither.
We had a look f.i. at the DataCite metadata schema (v3.1<http://schema.datacite.org/meta/kernel-3/doc/DataCite-MetadataKernel_v3.1.pdf>) where this is implemented with 'relationType' and controlled list values such as IsSupplementTo / Continues / IsVariantFormOf / IsOriginalFormOf etc. As an interim solution we were thinking of setting (external) links as 'Related URLs', however, there might be more clever ways to represent internal repository relations.
Maybe there is a way to take advantage of DataObj::EPrint's builtin *_thread (or get_all_related) methods?
Thanks in advance and sorry if it has been discussed (resolved?) so far, we were not able to find a proper solution in the list archive.
Greetings from Vienna,
Elena & Gertraud
Elena ?imukovi?, M.A.
Elektronisches Publizieren und Open Access
Electronic Publishing and Open Access
Vienna University of Economics and Business
Welthandelsplatz 1, 1020 Vienna, Austria
Tel.: +43 1 31336-5148
E-Mail: elena.simukovic at wu.ac.at<mailto:elena.simukovic at wu.ac.at>
-------------- next part --------------
An HTML attachment was scrubbed...