Dear Peter,
I will briefly describe our setup which is "non traditional".
We have two communities at our repository:
- one community uses "external" handle server;
- the other uses the "bundled" handle server.
Another requirement is that we must be able to modify (even create)
specific handles
Il 15/11/2014 02.57, Mark Diggory ha scritto:
...
I'm not sure if https://jira.duraspace.org/browse/DS-1637 really meets
the design goal to split off the Handle service entirely from DSpace.
It still looks to be a plugin to the existing local handle server.
Yes the remote handle service plugin
Peter,
The way that the Handle service is designed in general, your always going
to need a separate "Handle Service" for "all the handles under one or more
prefixes".
For an organization, this could be a standalone service that maintains
mappings for prefixes (and subpaths in suffixes) it assigns
As discussed on #dspace, one important thing to keep in mind is that
DSpace does Handles "backwards": it supplies a class for the Handle
server to load, which queries DSpace's database for Handle resolution.
I believe that what was envisioned by CNRI as typical would be for
things to work the other
Hi All,
I've been reading up on the various configurations that you can run DSpace
and the handle service in, and I was wondering if people would be willing
to share their experiences with "non traditional" set ups.
So, the out-of-the-box traditional setup, that I'm guessing 99% of us use
is to r
5 matches
Mail list logo