I got a partial fix thanks to an off-list response from Hugh Barnes <
[email protected]>.  Following this fixed our identifiers, though
the contents of <request> tag still refer to the internal IP.  See below:

We have our Dspace admin outsourced, but they just fixed some “localhost”
> value instances we had in our OAI-PMH output identifiers. Feel free to
> share with the list if it works and no-one else has suggested this.
>
> So our sysadmin changed a setting in config/modules/oai.cfg:
>
> identifier.prefix = ${dspace.hostname}
>
> (${dspace.hostname} is apparently set in dspace.cfg to the correct string
> value)
>
> The important part you may be missing is that the change doesn’t take
> immediate effect. This morning (Friday here!) a restart of Dspace happened,
> presumably on  a cron. Don’t think that’s an everyday occurrence. Also, I
> suspect a restart isn’t strictly necessary, there’s probably a script that
> will do it if restarting is an issue.
>
> Then apparently he ran “{…..}/bin/dspace oai clean-cache” after the
> restart.


It was either the reboot or the clearing of the oai cache that did the
trick, because I'd tried that value for identifier.prefix at some point in
my tinkering.
I then ran
[dspace]/bin/dspace oai import -c
and the identifiers were correct.


On Thu, Oct 10, 2013 at 2:35 PM, Jason Sherman <[email protected]> wrote:

> I've done quite a bit of searching and haven't quite figured out a
> solution to my problem.  Some info:
>
> Our dspace server uses a reserved (NATed) address.
> handle.net communication and HTTP requests are run through an
> internet-accessible front end server.  I've really not had any issues with
> it since I set it up, but now I'm interested in using the OAI interface and
> I'm running into some interesting behavior.
>
> When I do
> request?verb=ListMetadataFormats
>
> I get a response like this:
> <responseDate>2013-10-10T10:40:03Z</responseDate>
>     <request verb="ListMetadataFormats">https://10.x.x.x/oai/request
> </request>
>     <ListMetadataFormats>
>         <metadataFormat>...
>
> Where 10.x.x.x is the internal address of the dspace server.
>
> When I do
> request?verb=ListIdentifiers&metadataPrefix=oai_dc&set=com_11076_1
>
> I get a response like this:
> <responseDate>2013-10-10T12:11:24Z</responseDate>
>     <request verb="ListIdentifiers" metadataPrefix="oai_dc"
> set="com_11076_1">https://10.x.x.x/oai/request</request>
>     <ListIdentifiers>
>         <header>
>             <identifier>oai:dspace.library.usao.edu:11076/3</identifier>
>
> Where request is still the internal address, but identifier is what I
> would expect.
>
> When I do
> request?verb=ListRecords&metadataPrefix=oai_dc&set=com_11076_1
>
> I get a response like this:
> <responseDate>2013-10-10T12:11:30Z</responseDate>
>     <request verb="ListRecords" metadataPrefix="oai_dc" set="com_11076_1">
> https://10.0.253.47/oai/request</request>
>     <ListRecords>
>         <record>
>             <header>
>                 <identifier>oai:dspace.usao.edu:11076/3</identifier>
>
> Where request is still the internal address, and the identifier refers to
> the hostname of the internal server on our network.  This name isn't
> anywhere in our dspace configs.
>
> I've tried various combinations of the following configuration changes:
> in [dspace]/config/modules/oai.cfg
> ore.authoritative.source = oai
> identifier.prefix = dspace.library.usao.edu
> dspace.oai.url = https://dspace.library.usao.edu/xmlui
>
> [dspace]/config/oaicat.properties
> OAIHandler.baseURL = https://dspace.library.usao.edu/oai
>
> [dspace]/bin/dspace oai import -c
> Has no effect.
> --
> Jason Sherman
> Systems Librarian
> University of Science and Arts of Oklahoma
> 405.574.1340
>
>
>


-- 
Jason Sherman
Systems Librarian
University of Science and Arts of Oklahoma
405.574.1340
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to