Mixing open and restricted access materials

Over the Christmas break I read the interesting Global Ireland: same difference. And, in my convalescence, I have been looking at other materials on this topic. I had a look at OAIster. A search on Ireland and globablization returned quite a few results. I was interested in browsing through the results on the first page: six of the items were immediately available to me; four were not: I was directed to a publisher’s splash page.
Now, I had, mistakenly, thought that OAIster focused on open access material so was surprised to see this. Looking at historic snapshots of the site on the Wayback Machine, I found the following on the 16th July 2006. There had been a stated focus on ‘freely-accessible’ material, but this changed.

OAIster is a project of the University of Michigan Digital Library Production Service. Our goal is to create a collection of previously difficult-to-access, academically-oriented digital resources (what are digital resources? why is the “freely-available” designation gone?) that are easily searchable by anyone. [OAIster Home]

Following the link [not working in the extract above] about the ‘”freely-available” designation’ brings you to the OAIster Collection Development Policy, which is admirably clear, and reasonable for a service provider in their situation. Basically, as sites mix freely-accessible material and restricted-access-material in their harvestable sets, there is a heavy processing burden on an aggregator who wants to reliably separate these out. And OAIster has decided it is not going to do this work.

Often, data contributor repositories that we harvest contain records that point to both freely-available and restricted-access digital resources. Sometimes repositories partition these records into OAI sets (e.g., “freely accessible texts”) that can be easily harvested, and sometimes they do not. When they do not, additional effort on our part is required to selectively filter only the freely-accessible digital resource records. This is entirely dependent on the records themselves– the metadata itself must contain some indication of restriction policy (e.g., “This material is accessible to the public, freely and without charge.”) in order for us to perform filtering. Records frequently do not contain this information and only by following the link to the digital resource does availability become clear. Consequently, the decision to keep or not keep an entire repository’s records based on the discovery of some restricted records has been challenging. [OAIster | Collection Development Policy]

This is a reminder of the variety of collection development practice over institutional repositories which I have spoken about before (in relation to Minnesota and the Open University). I notice that the Open University self-describes its repository as Open Access, yet it contains a large amount of restricted access materials.
Related entries:

One thought on “Mixing open and restricted access materials”

  1. All right, so what’s the fix and who’s going to browbeat the Big Three platforms into implementing it?
    I just started talks on an IR project this morning that will HAVE to be almost completely closed (music performances submitted as part of music Ph.Ds; the copyright is in the underlying compositions, which aren’t the candidate’s). Some small part of it may be openable, but if I don’t take the closed stuff, I don’t get the open stuff. So “don’t accept anything that isn’t OA” is a lousy answer.
    Rights metadata is in a parlous state. As a repository-rat, I can’t fix that; the standards aren’t there, and neither is the will to impose rights standards on Big Three developers.
    OAI-PMH, with its (unnecessarily and unwisely narrowminded, IMO) emphasis on metadata, can’t easily communicate what’s up with the bitstreams. DSpace’s implementation of OAI-PMH is unable to distinguish between open and closed items; I often describe this as “metadata left flapping in the wind.” I can’t speak for EPrints or Fedora, but I hope they’re smarter!
    Again, where’s the fix?

Comments are closed.