In collection metadata: When OA toggle is on, and license type = 'Other', user should be required to provide a license URL
Context
A URL should be required if an Other license type is selected in Collection metadata.
Proposal
Make the license URL writeable when user selects Other license in Collection metadata. Write this URL into the collection XML as such:
<license xmlns:xlink="http://www.w3.org/1999/xlink" license-type="open-access"
xlink:href="https://www.ncbi.nlm.nih.gov/books/NBK138602/">
Design
Acceptance criteria
-
In a Collection Component, System Admin, Org Admin, Editor can select Other as a license type in the dropdown, AND when they do be required to enter a license URL in the license URL free text box, AND -
The license URL will be saved and unchanged until the user modifies and saves their modifications to that license URL -
When a Collection is loaded, if user entered the Other license URL to Bookshelf https://www.ncbi.nlm.nih.gov/books, it will be written into the license in the collection metadata as such: <license xmlns:xlink="http://www.w3.org/1999/xlink" license-type="open-access"
-
When any chapter-processed book in a Collection, such as Help Bookshelf ( helpbookshelf
) in the NCBI Help Collection (helpcollect
), and a user enters the Other license URL to Bookshelf https://www.ncbi.nlm.nih.gov/books then it will be written to the collection metadata in every Help Bookshelf book part wrapper converted XMl as:<license xmlns:xlink="http://www.w3.org/1999/xlink" license-type="open-access"
Definition of ready
-
BCMS User Story / Context has been well defined -
The priority of the user story is specified and agreed -
Digital assets added (design, database scheme, mockups etc if relevant) -
Coko Technical Proposal approved by NCBI -
Testable Acceptance Criteria approved by NCBI -
Estimate of effort to complete (time or points) -
The issue has been broken down into development tasks (if necessary) -
Requirements Clarified -
The product owner and development team agree that the user story is ready for development -
NCBI adds “Dev_Ready”
Definition of done
-
All coding tasks are finished and implemented -
QA approved -
Deployed and tested on “ncbidev” (by Coko team) -
Deployed and tested on “ncbi” (by NCBI team) -
Acceptance Criteria Met
Implementation
Alternative approaches (if applicable)
Scheduling
-
Milestone is linked -
Iteration is linked -
Dependencies: ("None" or list issue numbers if relevant) -
Development estimate is added to issue time tracking