https://folio-org.atlassian.net/browse/ERM-683

@Owen Stephens

https://folio-org.atlassian.net/browse/ERM-685

@Ethan Freestone

Further ETA 2w 

• Some backend complications relating to how dates are stored

• UI setup to follow

• Dummy UI set up  

• Assume resources in KBART file are digital

  • though there may be Print Identifiers and Print Publish Date rather than digital equivalents: treat these as digital without the relevant fields)

  • no need to flag lacking publication date (missing identifier should already be reported)

https://folio-org.atlassian.net/browse/ERM-696

Blocked by https://folio-org.atlassian.net/browse/ERM-711

https://folio-org.atlassian.net/browse/ERM-434 / https://folio-org.atlassian.net/browse/ERM-644 

@steve.osguthorpe  / @Peter Böhm

Further code review changes requested.

Expected to push within the hour. 

https://folio-org.atlassian.net/browse/ERM-655

@steve.osguthorpe

https://folio-org.atlassian.net/browse/ERM-700

@steve.osguthorpe

.

https://folio-org.atlassian.net/browse/ERM-702

@steve.osguthorpe

https://folio-org.atlassian.net/browse/ERM-711

@steve.osguthorpe

Prioritise above https://folio-org.atlassian.net/browse/ERM-655

https://folio-org.atlassian.net/browse/ERM-703

May be required by https://folio-org.atlassian.net/browse/ERM-711

https://folio-org.atlassian.net/browse/ERM-698 / https://folio-org.atlassian.net/browse/ERM-699

Date format should reflect system locale in Edit (as used in View).  Stripes objects pass in the locale. May need separate library (such as moment) to extract the format without affecting value translation. 

https://folio-org.atlassian.net/browse/ERM-714

@Aditya matukumalli

Pick list explicitly conditionally hidden as part of ERM-683. To be reverted. 

https://folio-org.atlassian.net/browse/ERM-715

@Aditya matukumalli  / @Peter Böhm

Currently no UI validation in place.  Needs proper backend validation also. Some current experiences: 

• Backend, eg, is currently forcing decimal values to an integer (Grails autoconversion). 

• Entering more than 255 characters in text type returns null value.

Frontend validation messages to reflect the type permitted for the specific license term or supplementary information.

Backend validation currently happens after binding. Some extra non-trivial functionality would be needed to intercept raw JSON.  Some straightforward validation options to prioritise: 

• Required

• is RefData 

https://folio-org.atlassian.net/browse/ERM-713

@Gill Osguthorpe @Owen Stephens

Effectively a batch operation, exporting report to tabular format. Should be facilitated easily enough because of JSON handling / output.  New specific JSON file could be created for batch. License endpoints can be filtered by ID/OR. 

Selecting multiple licenses isn't currently possible.

• Basket is used for agreement resources. Is this an appropriate model for licenses as well. (May need to disambiguate resource and (potential) agreement basket in Agreements going forward.)

• Or would line-select checkboxes in search results work instead? Pagination could be a gotcha. 

Expected to come ready for licenses in Sprint 84, and packages etc before too long.