[
https://jira.duraspace.org/browse/DS-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-766:
---------------------------
Status: Open (was: Received)
This issue was discussed in the DSpace Developers Mtg on April 6, 2011:
[20:08] <kompewter> [ https://jira.duraspace.org/browse/DS-766 ] - [#DS-766]
OAI-PMH non-persistent oai identifiers - DuraSpace JIRA
[20:08] <kshepherd> hmm
[20:09] <kshepherd> not so sure about 766
[20:09] <kshepherd> it's true that "persistence" as a term is overused somewhat
[20:09] <kshepherd> the same could be said of canonical handle urls, bitstream
urls, etc
[20:09] <tdonohue> To me, it seems like with Ds-766 should point at Handles (if
a handle server is installed), otherwise should point at 'dspace.hostname'
[20:09] <richardrodgers> indeed
[20:10] <richardrodgers> relative to the harvester, the host is important as
source info
[20:11] <tdonohue> that's true.
[20:11] * keithgilbertson ([email protected]) Quit
(Quit: keithgilbertson)
[20:11] <tdonohue> so, do we have recommendations here? Is this a "won't fix"?
Or a "needs more analysis"?
[20:12] <richardrodgers> tdonohue: the latter, I'd say
[20:12] <kshepherd> yep +1 needs more analysis
[20:12] <mhwood> Agree, it sounds like something to look into.
[20:12] * JRhoads ([email protected]) has joined #duraspace
[20:12] <richardrodgers> I'd be curious how, e.g. Fedora repos do it....
[20:12] <kshepherd> and if we all chip in with our opinions in the comments,
that won't hurt either :)
[20:12] <tdonohue> ok. Ds-766 summary: Needs more analysis, suggestions of a
better way to do this. Also needs a volunteer
> OAI-PMH non-persistent oai identifiers
> --------------------------------------
>
> Key: DS-766
> URL: https://jira.duraspace.org/browse/DS-766
> Project: DSpace
> Issue Type: Bug
> Components: OAI-PMH
> Reporter: Claudia Jürgen
> Priority: Critical
>
> The oai identifiers are supposed to be persistent. In DSpace they are
> constructed with the dspace.hostname, which might change easily.
> There should be a seperate configuration parameter to be used for it and the
> implications of changing it should be well documented, big warning sign.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel