Date
...
Resource Access has additional report requirements
App Interaction: ERM + eUsage + Reporting
The eUsage app would like to include a statistics summary that would require joining data between ERM and eUsage modules. Rather than having the app know how to join its data to another app, should they try to leverage the joins that the LDP is already doing? How might that work?
...
- can we automate data dictionary with info from the dev API documentation?
- From Nassib: data dictionary is a vague concept, we should agree on what it means. What are we going to mean by "data dictionary"?
- Option 1 ("Data Dictionary"): documentation of the attributes in the LDP (fairly common definition); an attribute is a column in a table in a relational database; "documentation" would include values of the fields, what they are, etc. Could write it from a librarian point of view. It's complete documentation - everything you need to know to be able to use it in queries. Could take the form of just filling in the comment field of the attributes in the database. Note: we want to do better than the FOLIO documentation, that is too minimal and our data is slightly different. Would be nice to include where the data came from. (Maybe people could help.)
- Option 2 ("Data Dictionary + Glossary"): FOLIO needs dox, LDP needs dox, sort of covering the same attributes (pretty close). What if there was a third document - a data dictionary, kind of like a glossary of librarian terms. Term is the technical term for librarians, has definition, then LDP and FOLIO dox could point to the glossary. Counterpoint - librarians would not really agree on the definitions. But if we had definitions, we could use technical terms in the data dictionary without having to be too general. This would also mean FOLIO can share our documentation work.
- One model of the elements we would need for the LDP documentation is
. If Option 1, this would be the same as the data dictionary. If Option 2, LDP dox would follow this specification and refer to the glossary, which could be called the data dictionary. This information will definitely be in the comments, no matter what we call the data dictionary.Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-1551 - The main data dictionary issue is
.Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-1414
Resource Access
Action items
- add a user story to the JIRA issue about storing effective location in loan (UXPROD-1432)
...