| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Requirements and use cases
| Requirement | Status | Use cases | ||||||
|---|---|---|---|---|---|---|---|---|
| (Sample) Library must specify which fields from the Instance, Organization, PO and POL must be included in a given template |
| Different vendors may require that different bits of information may need to be included on claim forms. Libraries need to be able to specify what FOLIO data needs to be included in a given claim template. | ||||||
| (Sample) Library must be able to specify the layout and the order in which fields appear |
| |||||||
| (Sample) Library must be able to save templates for future use |
| |||||||
| Appropriate templates must be available for use when generating or printing claims |
|
Questions
| Question | Status | Conclusion | Comments | ||||||
|---|---|---|---|---|---|---|---|---|---|
Does the type of order affect the data needed in the claim (i.e. different order type = different claim template?) E.g Serials vs. standing orders vs. firm monographic orders? Material types? Per vendor? Combination? |
| ||||||||
| Do the different divisions manage claiming differently? Do they capture or provide different information? |
|