Hi,

I have been involved in testing DSpace to harvest a collection not 
hosted in DSpace, but which is OAI compliant. We have been successful in 
doing the harvesting, but not successful in having the DSpace record 
point to the correct external record.

The issue is that DSpace assigns a URL of the form
http://hdl.handle.net/123456789/xxxxx
to dc.identifier.uri
although dc.identifier appears correctly, e.g. 
http://scaa.usask.ca/gallery/northern/image.php?ID=10857 (the main 
problem is that the correct identifier is not hyperlinked, and doesn’t 
appear in the simple view)

As you can see, we are running a test implementation of DSpace and have 
not implemented the handle server, hence the “123456789” prefix. But I’m 
not sure that’s the only issue.

What I’m wondering is:
- Is there a way, by populating appropriate fields on the repository 
side or by configuring DSpace, or otherwise, to have the correct 
identifier (URL) show up in dc.identifier.uri, especially for the 
purpose of the test implementation?
- Will implementing the handle server actually solve the problem? It’s 
not clear to be how this will work, since wouldn’t we need to register a 
prefix (or at least set up a mapping) for each external collection? As 
may be obvious, I'm not too familiar with how handles work.

As additional background, I did also test with a repository using the 
OAI identifier format, i.e. oai:domain:id. The element dc.identifier 
resolves correctly, but dc.identifier.uri still uses the non-functional 
handle. On the other hand, harvesting from a DSpace collection works 
properly, with dc.identifier.uri being populated with the handle 
assigned by the other DSpace instance.

In case it makes a difference, we are running DSpace version 1.6.0.

Thanks for any guidance on this.

Tim

-- 
Tim Hutchinson
University of Saskatchewan Archives
301 Main Library, 3 Campus Drive
Saskatoon, SK  S7N 5A4
tel: (306) 966-6028
fax: (306) 966-6040
e-mail: [email protected]
web: http://www.usask.ca/archives/ 



------------------------------------------------------------------------------

_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to