The Scholarly Works Application Profile (SWAP) uses the FRBR model
(work, expression, manifestation, item) and its relationships, to enable
identification of the appropriate version (expression) and navigation
between versions.
Also worth noting that the Version Identification Framework project is
including 'Recommendations for future [repository] software development'.
Rosemary
SWAP:
http://www.ukoln.ac.uk/repositories/digirep/index/Eprints_Application_Profile
VIF: http://www.lse.ac.uk/library/vif/Framework/index.html
Ian Stuart wrote:
> Antony Corfield [awc] wrote:
>
>> Software engineers have been using repositories or versioning systems
>> for many years (e.g. cvs http://www.nongnu.org/cvs/ and svn
>> http://subversion.tigris.org/ ) where code (content) can be modified
>> by authors and each version saved with comments. Team integration,
>> roll back to previous versions and branches offering different
>> flavours and tagged releases (publication) are at the core of
>> versioning systems.
>>
>> Whilst IRs may be seen more as content (and metadata) archives where
>> the 'finished article' can be made available, a common framework for
>> versioning which incorporates some of the above would be desirable.
> I think that one of the factors in this is that the repository is seen
> as an end-user database for displaying things, where there is an
> emphasis on "archive" rather than "repository", where each state is a
> distinct and inviolate thing that needs to be maintained as distinct
> from past and future incarnations.
>
> Yes, there is a need to be able to manipulate the content held in a
> research database more easily, but this is at odd with the "archive"
> premis above.
>
> I have a personal belief that the current repository concept is
> flawed, and that institutions should provide a repository for "work in
> progress", complete with descriptive data to associate it with the
> appropriate research grants, researchers, departments, funders, etc.
>
> I believe that the thing we call an "institutional repository" should
> be a slice into this data-corpus, not a database in it's own right.
>
> In this approach, one can use the likes of Google Docs for document
> editing... which provides versioning and so forth :)
--
Rosemary Russell
UKOLN, University of Bath
Bath BA2 7AY
http://www.ukoln.ac.uk
+44 1483 560342
|