Campaign: Putting user at centre of definition

6, Define repository as part of the user’s (author/researcher/learner) workflow

It is important to take account of user's workflows when defining a repository so it is not considered a system that is removed from the users daily routine.

Submitted by (@andymcgregor)

Voting

29 votes
Active

Campaign: Putting user at centre of definition

Repositories are dead, long live repositories

The current repository technology is library/cataloger centric: items are uploaded (usually by a cataloger, not the author), and most of the meta-data is added by a subject specialist. In this model, the author-as-depositor is (at best) just an initiator for a deposit process. A better solution would be to move towards a Combined Research Information System [CRIS], where the academic can organise their areas of interest ...more »

Submitted by (@ian.stuart)

Voting

18 votes
Active

Campaign: Definiton rules

Say what we mean: stop using the term repository

When we use the term repository in the context of JISC(and other repository networks) essentially it means making content (in our case produced as part of research, learning and teaching) available over the network so it can be shared and used. But the word doesn’t say that. The word says store. We should be saying what we mean. We should really be talking about making content available on the web? And if concerned with ...more »

Submitted by (@r.bruce)

Voting

19 votes
Active

Campaign: Putting user at centre of definition

5, Focus on services to users enabled by digital collections in repositories

(i.e. emphasise benefits)

Submitted by (@andymcgregor)

Voting

13 votes
Active

Campaign: Consistency

Consistency between repositories is not an end in itself; it is only important if it is a requirement of real value-added servic

Interoperability needs to be motivated by service requirements, not fetishized as an end it itself.

Submitted by (@dempseyl)

Voting

20 votes
Active

Campaign: Repository functions

The repository should be more like "part of the web"

This is the Andy Powell worry; we have made the repository too much of a "special thing" operating under "library rules". Make it more like Slideshare. I'm going to express this another way...

Submitted by (@c.rusbridge)

Voting

17 votes
Active

Campaign: Consistency

There are feasible and worthwhile approaches which will improve the consistency with which repositories share metadata

As part of our work to "examine the feasibility of approaches to improve the consistency with which repositories share material", we are looking at this in regard to 3 areas: metadata (this idea), the materials themselves and descriptions of repository policies (e.g. on IPR) [materials and policies appear as separate ideas].

Submitted by (@nf0000)

Voting

19 votes
Active

Campaign: Putting user at centre of definition

Make the repository work for the user, not the other way round

I guess this is the workflow idea again, but stated another way. Don't get too hung up on "workflows", as in the e-science meaning (kepler, taverna et al). This is about making the repository fit in what people are trying to do, eg write the article, keep multiple versions, share with their colleagues in other institutions...

Submitted by (@c.rusbridge)

Voting

14 votes
Active

Campaign: Repository functions

The repository/library should provide support in the publishing process

Another from the Research repository System (RRS) blog posts: Publisher liaison is maybe controversial. But why shouldn’t the RRS staff (or your library) support you in dealing with publishers? The RRS wants your articles and your data, and should help you negotiate and reserve the rights so that they can get them. So publisher liaison would include rights negotiation, submission to the publisher on your behalf of a ...more »

Submitted by (@c.rusbridge)

Voting

14 votes
Active

Campaign: Definiton rules

1, Definition assumptions

Definition should not make assumptions as to implementation architecture i.e. whether deposited collection(s) held at institutional or network level

Submitted by (@andymcgregor)

Voting

17 votes
Active

Campaign: Consistency

Broad principles not tight prescriptions

The changes in technology, the diversity of cataloguing practice,

the diversity of ownership and legal considerations and the

possibilities for metadata to be created remotely all mean that

acceptable and achievable recommendations for consistency between

repositories are likely to be broad principles with examples of good

practice rather than prescriptive rules or precise recommendations.

Submitted by (@nf0000)

Voting

16 votes
Active

Campaign: Repository functions

Allow the user fine-grained disclosure/access control to repository objects

If the repository is to become anything other than a final destination for public objects, then the user needs control over access. This control must be able to ALLOW access to the objects by colleagues, wherever they work, as well as prevent access by others.

Submitted by (@c.rusbridge)

Voting

14 votes
Active