Hi Peter, all,
the authority framework was introduced many years ago so it is quite
obvious that we have forgotten about the initial implementation.
When Larry Stone and me introduced the framework the two targets were
the Harvast Catalyst expert directory and DSpace-CRIS, see this
presentation at OR 2010
http://eprints.rclis.org/15170/1/OR2010-light.pdf
as far as I know the source code used by Harvard is not publicly
available and since then Larry left his job at Harvard.
What is still available and used in production by more than 70
institutions is the authority used to integrate the basic dspace data
model with the extension provided by DSpace-CRIS.
The relevant code is here:
https://github.com/Cineca/DSpace/tree/dspace-5_x_x-cris/dspace-cris/api/src/main/java/org/dspace/app/cris/integration
most important class
https://github.com/Cineca/DSpace/blob/dspace-5_x_x-cris/dspace-cris/api/src/main/java/org/dspace/app/cris/integration/CRISAuthority.java
https://github.com/Cineca/DSpace/blob/dspace-5_x_x-cris/dspace-cris/api/src/main/java/org/dspace/app/cris/integration/RPAuthority.java
etc.
summarizing, dspace-cris allows you to maintain your authorities:
creating, editing and deleting record. The authority framework allows
you to link a dspace item to a DSpace-CRIS entity.
Best,
Andrea
Il 21/01/2016 20:41, Peter Dietz ha scritto:
Hi All,
The DSpace Authority framework currently has one implementation,
ORCID. And, the documentation for the Authority Framework, offers some
guidance on extending this, to build your own implementation to wire
up other Authority sources. I was wondering if anyone has done this
yet, and had some lessons learned?
https://github.com/DSpace/DSpace/tree/master/dspace-api/src/main/java/org/dspace/authority
Perhaps, this is loosely a follow up to my previous "nested metadata"
discussion. Though we don't need to support nested-metadata for this,
just a trustworthy source of data.
https://groups.google.com/d/topic/dspace-tech/z7Nibc-3rJw/discussion
At this moment, we don't plan on integrating with an existing data
store, but would be creating a data store from scratch, and then
populating that store from a local person provider (database, ldap,
csv, ...). Then, building an authority-service to use that new data
store. It seems like a lot of work, just for the purpose of having
auto-complete for a given metadata field.
________________
Peter Dietz
Longsight
www.longsight.com <http://www.longsight.com>
[email protected] <mailto:[email protected]>
p: 740-599-5005 x809
--
You received this message because you are subscribed to the Google
Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
--
Andrea Bollini
International Business Development, Deputy Leader
Open Source & Open Standards Strategy, Head
Cineca
Via dei Tizii, 6
00185 Roma, Italy
tel. +39 06 44 486 087 - mob. +39 348 82 77 525
http://www.cineca.it
--
You received this message because you are subscribed to the Google Groups "DSpace
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
