EntCollNet / BugFlow

Bug flow is a community resource for entomological collection digitization workflows and modules.
Creative Commons Zero v1.0 Universal
22 stars 5 forks source link

Module 4F: Slide Label/low-res Imaging [1st Draft Completion List] #72

Closed tmcelrath closed 3 years ago

tmcelrath commented 3 years ago

Module 4F: Slide Label/low-res Imaging

tmcelrath commented 3 years ago

https://www.idigbio.org/wiki/images/3/30/Scanning_Microscope_Slides_Oboyski.pdf - added 02MAR2021

tmcelrath commented 3 years ago

Contact: langane@si.edu

tmcelrath commented 3 years ago

@EMTuckerLabUMMZ using Inselect to crop and save: https://drive.google.com/drive/u/0/folders/1ptvL7xFldeErq2AvU62xIFbeB3enpey-

dryopoiddarling commented 3 years ago

Done with 132c300 ~~T4 - remove "maintain sequence of slides" Switch T4 and T6~~

dryopoiddarling commented 3 years ago

Move text for T1 "Explanation and Comments" to "Module Purpose" with 5ae62e9

debpaul commented 3 years ago
debpaul commented 3 years ago
dryopoiddarling commented 3 years ago

Done with 132c300 Reorder and rewrite t4-t7 to take into consideration data that is communicated in location in box. Consider whether they need to be reorganized or not, based on the workflows of the institution.

dryopoiddarling commented 3 years ago

Done with 132c300 Reverse T11 and T12

debpaul commented 3 years ago

Added with 8590d49 For T9. Suggest referring to better practices involving image file names. Best practice would not put metadata like taxon name in the file name (since this could change and then makes image tracking and handling more challenging). One needs to depend on one's database to know what the images depict.

Task Name Now: Save/name image file in a standard, institutionally determined format, if necessary. Some databases do not need this step.

Task Name Suggestion: Save/name image file in a standard, institutionally or project-specific determined format, if necessary. Best practices would use only alphanumeric identifiers and avoid putting any specific metadata like genus or species names in the file names because these data could change.

Explanations and Comments Now: A file-naming scheme that mirrors the collecting event identifier is sometimes used. Examples might include: "country code"+"state code"+"verbatim directions"+"collector name"+"date"+"serial identifier", or a subset of these. This can also be done using batch renaming using programs like Adobe Bridge, IrfanView (free), or Inselect (free). Inselect can also parse out multiple slides in one image, read QR codes, and rename files based on the embedded information. DO NOT USE SPACES IN FILENAMES

Explanations and Comments Suggestion: A best practice file-naming scheme would use only the number that comes form the camera, possibly concatenated using an underscore "" with other numbers such as location in the collection or other identifier that would likely not change such as the relevant collecting event identifier. Examples might include: "camera number" "location in collection" or what is needed to track these in your collection. This can also be done using batch renaming using programs like Adobe Bridge, IrfanView (free), or Inselect (free). Inselect can also parse out multiple slides in one image, read QR codes, and rename files based on the embedded information. Best practice avoids spaces in image file names. Note that using examples like: "country code"+"state code"+"verbatim directions"+"collector name"+"date"+"serial identifier" can work, but note that if any of those data change, then the file name will not help to understand what is in the image or help to find images.