Function Requirement Requests
Requests for IR Functionality
The table below is merely an inventory of Function Requirements Requests received by FLVC in the lead up to the July 2016 FLIIRT meeting. The numbers represent the order in which the requirements were added to the table: no ranking or prioritization is implied. All submitted Function Requirements Requests submitted before July 2016 IR Camp (absolute deadline for submission is the end of day Wednesday, July 20) were assembled and discussed at the meeting.
|Functional Requirements, in order of receipt|
|NUMBER||TITLE||DESCRIPTION||LINK TO FORM|
|FSU-1||Implement Islandora Entities Solution Pack||Status: This is implemented on ir-test, fau-test, fgcu-test, ucf-test, and fsu-test. FLVC made code changes to make linking configurable and to allow departments to link to departments. Instructions on this are posted to https://fliirt.wiki.flvc.org/wiki/index.php/FL-Islandora_IR_Documentation . |
|FSU-2||Implement Islandora Altmetrics Utility Module (IAUM)||Status: This is implemented on ir-test. You can see the Altmetrics donut on object with a DOI. For example, this object: https://ir-test.digital.flvc.org/islandora/object/islandora%3A4023 .|
|FSU-3||Create an Author Dashboard with usage metrics about contributing authors' objects in the repository||Description: The Author Dashboard would enable authorized users (faculty, staff, students) to view usage statistics on objects they have contributed to the repository.|
Status: Not started.
|FSU-4||Integrate FL-Islandora authentication with institutional authentical protocols (e.g. CAS, Shibboleth, LDAP, etc.) and Islandora Entities Solution Pack||Status: Not started. As of Fall 2016, there is a wider FLVC project to set up central authentication for all the stakeholder universities and colleges. It would be great to wait until that is complete, and then authenticate against that central authentication service. The alternative of working with several different university/college systems is not feasible. However, if Islandora development begins with just a single institution, a significant chunk of that development work could be transitioned to central authentication later.||https://drive.google.com/folderview?id=0BwbriDSNjBiJVGFMLXRIcjZ3bEE&usp=sharing|
|FSU-5||Implement automated monthly Readership Reports in FL-Islandora||Description: Implement functionality to automatically generate and send simple readership reports to the institutional email addresses of authors who have contributed work to the repository.|
Status: Not started.
|FSU-6||Implement Native Islandora Submission functionality to allow authenticated users to submit works directly within an FL-Islandora IR instance||Status: Not started.||https://drive.google.com/folderview?id=0BwbriDSNjBiJVGFMLXRIcjZ3bEE&usp=sharing|
|FAU-1||Implement Islandora Entities Solution Pack||(duplicates FSU-1)||https://drive.google.com/open?id=1yQu_nRuHa2QEMJHqK-ulZWcIAuwNWb-8tvwQqHMCDPM|
|FAU-2||Implement Islandora Altmetrics Utility Module||(duplicates FSU-2)||https://docs.google.com/document/d/1os8YYJ9oBmb98g2HK4EeHZOPGvXGO_lsaMMMUujXiCQ/edit?usp=sharing|
|FAU-3||Create an Author Dashboard with usage metrics about contributing authors' objects in the repository||(duplicates FSU-3)||https://docs.google.com/document/d/1ELsDwr2S8hhmxMgU4-cHyJgGHmkeaFK_VL3LrMR35_Q/edit?usp=sharing|
|FAU-4||Integrate FL-Islandora authentication with institutional authentical protocols (e.g. CAS, Shibboleth, LDAP, etc.) and Islandora Entities Solution Pack||(duplicates FSU-4)||https://docs.google.com/document/d/1LYGQE71hQgDSLO5zOLBAND58A14Jy-HrbkmRgDFPZa8/|
|FAU-5||Implement automated monthly Readership Reports in FL-Islandora||(duplicates FSU-5)||https://docs.google.com/document/d/1SLaRqhbS5zvhlaIJu2u_qECz3rM01WPzp2IGac79J5Q/|
|FGCU-1||Integrate FL-Islandora Entities with ORCID registry||Status: It's been decided to store ORCID identifiers in the MODS like so <name><nameIdentifier type="orcid">ORCID-identifier-goes-here</nameIdentifier></name> |
Next Steps: Work towards interfacing with the ORCID API should begin. It's possible to read public information through an open API. Reading other information and writing to ORCID requires authenticating and storing authentication information and requires the repository to have a paid membership in ORCID. As of Fall 2016, no institution has a paid membership in ORCID.