enarratives Topic 4: How to handle Approvals/Authorisations?

[rondlg]

DISCUSSION POINTS: There is a field on the Details tab (y/n) called “Approval”, there is a whole tab called “Authorisation” (AllAutTab) and also the Tasks tab. How should we standardise the process for recording approvals?

[rondlg]

DECISION(S): We are eliminating the Approval? Field (NarFMNHApproval_tab) from the Contributors group box on the Details tags and using the Authorization tab (AllAutTab) for all “approvals.”

DATA CHANGES: Data Changes Doc Pre new development: #10; #4 Post development:

[rondlg]

In collaboration with NMAI the Approvals tab is now called Actions. Available in v9

[rondlg]

Data transferred to AllAutTab fields

Mapping:

• NarContributorRef_tab.irn ->AutByRef_tab.irn
• NarFMNHApproval ->
• • Yes -> Approved
• • No -> Not Approved
• NarContributorRole ->AutAction_tab
• • Content Review-> Content Review
• • Image Review -> Image Review
• • Editor -> Editor
• • Content Verifier -> Content Review

[rondlg]

If might be possible to extract the date from audit for some records but this is a "nice to have" not a "need to have". Moving forward the AutActionDate0 field should be filled in.

[rondlg]

The last step is to make the NarFMNHApproval field readonly

[rondlg]

upload csv: approval.csv