Naming convention for digi app export files

[PipBrewer]

Template for isues/tickets in DigiApp

What is the issue ?

We need a naming convention for the digitisers to follow when exporting records from the digi app each day.

Why is it needed/relevant ?

A digitiser may export more than one batch of records from the digi app each day. At the moment there is no file naming convention for these export files and so it is difficult to tell if these are duplicates. We already have examples of exports from the same person on the same day - all with different types of suffixes. It is very confusing. Are they separate files, duplicates, issues etc?

Estimate level of effort required.

Easy

What is the expected acceptable result.

• [ ] Decide an acceptable convention
• [ ] Communicate this to Chelsea (and ask her to incorporate into workflow training and mention on AD Slack)
• [ ] Incorporate into documentation procedure on Github

[jlegind]

Matilde has accepted my suggestion-

A solution could be; [collection name] like NHMDHerba, then the [date] (yyyymmdd_). Then [hoursminutes] and initials .

Example: NHMD_Herba_20230621_14_05_MG.csv