Tick boxes when specimen or label obscured

[PipBrewer]

Some discussion has been going on with the collection managers and digitisers, but it looks like we should make a note of instances in the Digi App where the specimens and/or label will not be able to be imaged as they are obscured (has implications for reports to collection managers, status and for transcription). In Specify, I was thinking that if we add them as separate lines in the remarks table using controlled terminology, we should be able to run reports on them to send to collection managers to review. However, in the App it might be easiest to have tick boxes for these.

• @chelseagraham and Matilde to confirm with Jens S regarding the use of "Specimen obscured" and "Label Obscured" and provide a link here to that ticket with examples of how we use it and why.
• Decide where in UI boxes will go and what will look like
• Hand over to DigiApp team to implement
• Fedor to review the below steps and add additional/edit as needed
• Create tick box in UI for "Specimen Obscured"
• Create tick box in UI for "Label Obscured"
• Create columns for each of the tick boxes in the specimen table in the db
• These should then map to separate lines in the Remarks table in Specify and so need to update GREL script (how do we do this?)
• Fully test
• Demonstrate to Chelsea
• Update user documentation
• Update GREL documentation
• Update App documentation

[PipBrewer]

Sent email on 26/10/2023 to Fedor, Bhupjit and Jan asking whether it is theoretically possible to map notes from DigiApp to different lines in Remarks table in Specify.

Fedor's response: "Yes. If data like “Specimen Obscured” are separate tickboxes (or other kinds of input fields) that are stored into individual columns in the local app db then these can be sorted into columns that can be mapped to individual “Remarks” records (in reality: Collection Object Properties) associated with each specimen."

[chelseagraham]

just linking a ticket on the Herbarium board from which I can draw information relevant to this ticket NHMDenmark/Herbarium-Sheets-workstation#55

[chelseagraham]

@Gomismis as per our meeting with Pip, please add decisions (from NHMDenmark/Herbarium-Sheets-workstation#55) here, re-assign this ticket to Bhupjit, and then take this ticket off of our project board. Thank you.

[chelseagraham]

Current procedures (from @Gomismis document NHMDenmark/Herbarium-Sheets-workstation#55) include

• Flagging a specimen with visible labels and obscured or missing specimens as an MSO and scanning a data matrix with the controlled vocabulary "Specimen obscured" into the notes field. The number of barcode labels assigned corresponds to the number of visible labels. A single image is taken. (1.2, 1.6, 1.8, 4.1, 4.4)
• Flagging a specimen with obscured labels and obscured specimens as an MSO and scanning a data matrix with the controlled vocabulary "Specimen obscured; Label obscured" into the notes field. A single barcode is assigned. A single image is taken. (1.3)
• Entering a specimen with layered specimens and all information on the bottom sheet as a single specimen (no radio buttons selected) and scanning a data matrix with the controlled vocabulary "Specimen obscured; Label obscured" into the notes field. A single barcode is assigned. A single image is taken. (1.4, 1.7)
• Entering a specimen with layered specimens and the same label information as a single specimen (no radio buttons selected) and scanning a data matrix with the controlled vocabulary "Specimen obscured" into the notes field. A single barcode is assigned. A single image is taken. (1.5)
• Entering a specimen with label obscured as a single specimen (no radio buttons selected) and scanning a data matrix with the controlled vocabulary "Label obscured" into the notes field. A single barcode is assigned. A single image is taken. (1.7)
• Entering photos and drawings with associated data and scanning a data matrix with the controlled vocabulary "Non-botanical object" into the notes field. The number of barcode labels assigned corresponds to the number of visible labels. A single image is taken. (4.2)

I will just wait until this is confirmed (as the ticket that this is dependent (NHMDenmark/Herbarium-Sheets-workstation#55) on is not closed / completely resolved - needing input from @PipBrewer )

Confirmed by Pip

[FedorSteeman]

@bhsi-snm @PipBrewer Are the requirements of this ticket ready for me to start implementing, or who has the ball on this issue?

[FedorSteeman]

@chelseagraham What is the status?

[chelseagraham]

Confirming use of "Label Obscured" and "Specimen Obscured"

[FedorSteeman]

@chelseagraham Where on the UI are these two (?) tick boxes to be placed?

[FedorSteeman]

Placement specified here:
#439 (comment)

[FedorSteeman]

I just talked with @chelseagraham and I believed that these tickboxes are to be mapped to flag fields. However, looking through the ticket specification I can see these are to be mapped to collection object remarks (properties), so will do that instead.

Teased out the tasks that are relevant to me:

• Create tick box in UI for "Specimen Obscured"
• Create tick box in UI for "Label Obscured"
• Create columns for each of the tick boxes in the specimen table in the db
• These should then map to separate lines in the Remarks table in Specify

[FedorSteeman]

@chelseagraham Should I group these checkboxes together as proposed and use the caption "Specimen Flags" as per below?

[chelseagraham]

I think this works well. As Rebekka mentioned, they are not mutually exclusive, so the check boxes makes the most sense. :)

[AstridBVW]

This ticket was closed prematurely. Steps were missed, there still need to be made changes to the GREL script and mapping to accommodate the mapping of "Specimen obscured" and "Label obscured" to the DaSSCo remarks table in Specify.

[AstridBVW]

The GREL script has now been updated and pushed to github. It has been set up in a similar fashion to the notes field with a remark, source and date. The remark is "Specimen obscured" and "Label obscured" respectively, the source is "DaSSCo digitisation", and the date is the same as the cataloged date.

The mapping to the remarks table will be added with the next import.