Linking of Records:
Versions of objects in repositories can be organised in a variety of ways.
For example:
- All objects have their own record, and no records are linked together or make reference to other records.
- All objects have their own record, but if there is a relationship between two objects this is recorded by the repository and displayed to the user. This relationship may not be described, but one or both repository records refer to the other.
- Versions created as part of the development of a piece of work can be stored in a linear fashion, with one version being the latest, and previous versions linked to within that record.
- Versions of different format, such a word document and a PDF of the same thing, stored in one record.
These examples work if is the metadata for the record is consistent for all the objects stored within it. However, repository systems need to be able to cope with more complex relationships:
- A research paper that draws on a small set of survey results that are saved as a spreadsheet. Both are submitted for inclusion on the repository. Should the data file have its own record? Preferably not. It should be able to be stored in a record which represents the body of work that both pieces are components of.
This is consistent with FRBR. The data ideally would be described as supplemental to the research paper that is served, but should still have its own metadata, as it is a distinct object which different attributes. It is important to consider however what defines the overall boundary for a FRBR style collection of records or items. In FRBR terms this is the concept of 'work', and it is this that defines the scope for relationships within that work.
VIF recommends that repository systems are able at the minimum to be able to link objects that have a version relationship, and to provide a flexible architecture that allows objects to be stored and displayed in a way that reflects their version status in a workflow, such as the example of the data supporting the article given above.
Versioning within Repository Software:
Repository software platforms have differing approaches to version organisation. Here we have profiled the approach of three major platforms to versioning. This information will be of particular interest to those who have yet choose a repository platform, are thinking of migrating or have yet to upgrade their current software to the latest available:
Next Section:
Click to link to go to the FRBR page.