Page Comparison

Nassib has asked that we review a few more LDP table mappings and naming. 

(Explanation from a previous meeting)

At present, some table names use prefixes to remove ambiguity, e.g. /finance-storage/groups is mapped to finance_groups, while others do not use a prefix, e.g. loans, users, and groups, as they are considered to have a more general application.  In other cases, it may not be obvious whether a prefix should be used, e.g. requests.

The advantages of using a prefix are clarity and leaving "room" in the namespace for more similarly named concepts in the future to co-exist with the current tables.  The disadvantage is longer and more complex table names.

Now that queries are being developed, there will be an increasing number of dependencies on table names, and it is a good time to pause and give some thought to whether some of them should be changed, because it will be increasingly difficult to change them later without having to modify existing queries.

A spreadsheet with the table mappings and naming is linked here, and I would appreciate input from the Reporting SIG:

• LDP Table Naming
  1. Add table spaces to LDP tables by including prefixes in table names.  i.e. prefix would match module name? 

• Time to Rank your Reporting Clusters

Reminder: The MVP project managers are interested in getting all the MVP tickets ranked by each institution. If your institution has still not ranked the reporting clusters, please urge them to do so soon. We need this for both MVP and prioritization for what reports to build next within the Reporting SIG. Thank you!

Let's discuss some ideas for dividing our work into functional area report development teams:

• How to update your entry on the Reporting SIG Home Page to reflect our new subteam structure
• Reporting SIG now has 3 subteams to work on report prototype/query/testing: RA/UM Team, RM/ERM Team, and MM Team
• Team leads for each functional area stay on top of JIRA tickets/report development and communicate about progress
  • RA/UM: Vandana Shah is lead
  • MM: Kevin Walker is lead
  • RM/ERM: Sharon Beltaine and Scott Perry are leads
• use Reporting SIG home page to describe role for each Reporting SIG member in doing this work

1. Added the "consult" role to the Work Team Activity column.

Review and update Topics for Future Reporting SIG Meetings