The umbrella term "repository" conflates two very different kinds of services - services whose primary purpose is to preserve a type of media, and services whose primary purpose is to enable media to be shared and used by people. They don't look the same, they have different kinds of users and roles, they don't share the same concerns, and you use different language to talk about their features. Maybe we would get further ...more »
OK, I'll go the whole hog in relation to the RRS blog posts: At a very basic level, the RRS should [be associated with] a Persistent Storage service. Completely agnostic as to objects, Persistent Storage would provide a personal, or group-oriented (ie within the institution) or project-oriented (ie beyond the institution) storage service that is properly backed up. There’s no claim that Persistent Storage would last ...more »
Again, the Andy Powell idea. This one, I think, more about sharing, embedding, mashups. Think Flickr. Think sneep.
People who might create services from repository-based information
will be looking for simple human-readable information on the policies,
formats and metadata used by repositories. This is as important as
creating machine-readable interfaces.
A repository should be for content which is required and expected to be useful over a significant period. It may host more transient content, but by and large the point of a repository is persistence. While suggesting a repository should be a "full OAIS" has not proved acceptable to this group so far, investment in a repository and this need for persistence suggest that repository managers should aim to make their content ...more »
With acknowledgement for this idea to Owen Stephens' recent Tweet. My interpretation of this idea is that 'repositories' are best viewed as a 'type' of data store supporting a variety of services, embedded in various workflows. This fits nicely with Paul Walk's concept of a 'source repository' (see http://tiny.cc/FIHwc) being a simple system with complexity moved to specialised services. I suppose this approach isn't ...more »
Most early Institutional Repositories were research repositories. Some are purely repositories housing digital objects as in "Repositories are "collections of digital objects"". However, since one of the primary aims is to showcase the intellectual assets of the institutions (as compared to providing Open Access to peer reviewed journal articles) another model was 'hybrid'. The use as a bibliography (suggested both by ...more »
Managing data can be a big problem. Any data that might, for example, become supplementary data in an article, needs curating. Help the user by providing facilities to capture and hold intermediate versions of the data, ad the final public version.
This is a refinement of the current top-rated idea, based on one of my blog posts on research repository systems. Authoring support should include version control, collaboration, possibly publisher liaison, and be integrated with the repository deposit process. It does need object disclosure control, see below. Version control would support ideas, working drafts, pre-prints, working papers, submitted drafts undergoing ...more »
Repositories have a function as a source of the latest R&D knowledge, which should be exposed rather than kept hidden from users. Their content should be made available to wider audiences using current awareness tools such as RSS feeds. RSS also could help to increase the interest of authors as well, in order to boost the deposit rate.
Far from becoming irrelevant, metadata for repository items will
become more important but it will increasingly be created and assigned
remotely. This will be by automated procedures such as indexing and
text analysis and also by users and readers, through the use of
tagging mechanisms. These developments will have implications for
consistency between repositories and between items.
Again from the RRS blog posts: We don't think about identity management as part of the repository, although a really annoying early experience of DSpace related to the requirement for a completely separate identity. This seems to have been overcome by getting the librarian to do mediated deposit for you, but I don't have the feeling that the repository is well integrated into the institutional identity system. It should ...more »