Text Description:
A description, ideally written by the content creator, of an object's version status is a potentially clear way of making version identification straightforward.
Pros:
- If written by (or using information provided by) the content creator, trust can be taken in the quality of the information contained here.
- Relationships that are not easily described in a few words, or that exist outside of common relationships such as items in a publication cycle, are easily described if given a few sentences.
- The end user can use this information to make an informed decision about the appropriateness of the version at hand.
Cons:
- It would be hard to control the meaning of the text and therefore the end interpretation. Repository staff would have to be careful about what was allowed in such a field.
- A free text comment would need to be dated as newer objects with updated descriptions could be added. These could potentially make the content of previous free text descriptions out of date.
- Ensuring people fill this in cannot be taken for granted.
Recommendations:
Free text is an easy way to qualify other version information and to relate it to an object. It is also the easiest way to describe the relationships between versions.
However, care must be taken in the use of free text. For example, a text description calling something the 'last version' could easily be out of date.
It is essential to use this solution in conjunction with others
suggested by the framework to ensure the information given can be easily
understood.