Hi Bram et al, Thanks for your interesting work on integrating Fundref into DSpace.
In reviewing the information at https://github.com/atmire/RIOXX/blob/master/README.md#Areas-of-DSpace-manually-configured, I’m unclear as to how to properly add a rioxxterms.project field in input-forms.xml. Would it be something like the following? <field> <dc-schema>rioxxterms</dc-schema> <dc-element>project</dc-element> <dc-qualifier/> <repeatable>true</repeatable> <label>Funding information</label> <input-type value-pairs-name="rioxxterms_project">qualdrop_value</input-type> <hint>Select the funding sponsor and then add the respective funding code.</hint> <required>false</required> </field> As the funders info will be stored in the Solr authority index once the RDF file is imported, I’m unclear as to how to link the rioxxterms.project field with data. i.e. how do I link the qualdrop_value input to the datasource, as the value pairs would not be added to the input-forms.xml file? FYI, I have applied the RIOXX patch and will be loading the Fundref funders RDF file as documented. Cheers, Graham From: [email protected] [mailto:[email protected]] On Behalf Of Bram Luyten Sent: January 28, 2016 3:20 PM To: [email protected] Cc: DSpace Technical Support <[email protected]> Subject: Re: [dspace-tech] Re: Examples of extending/reusing Authority Control / ORCID In the RIOXX work, authority control is hooked up to fundref for funder identifiers. https://github.com/atmire/RIOXX/ https://jira.duraspace.org/browse/DS-2866 A special twist to the approach is that a funder is an authority in itself, but a project is an authority entry that also links to an entry in the funder authority. e.g. every project/grant identifier is stored together with a reference to a specific funder. best regards, Bram -- [logo] Bram Luyten 250 Lucius Gordon Drive, Suite B-3A, West Henrietta, NY 14586 Esperantolaan 4, Heverlee 3001, Belgium www.atmire.com<http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml> On 28 January 2016 at 10:35, <[email protected]<mailto:[email protected]>> wrote: Hi Peter, I have a couple of examples I've been trying out. One is a hookup to an LDAP source and the other is to a UK authority, Gateway to Research. https://github.com/alastairduncan/DSpace/tree/dspace-5_x/dspace/modules/additions/src/main/java/org/dspace/authority These use different visualisation of the results returned from that authority - this is due to existing xmlui implementations within DSpace. They are far from perfect and need some tidying up but may give you an idea of what you have to do. Alastair On Thursday, January 21, 2016 at 7:41:58 PM UTC, Peter Dietz wrote: 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. -- 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. -- 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.
