Finding Duplicates, The Henry Scenario
Identifying messages and examining the use case scenarios in Use_Case_Scenarios#Finding_Duplicates
James has a chat with Henry, a member of his curatorial staff, and tells him that he has made a commitment to produce a treatment of the genus Rubus for the Flora of North America. He asks Henry to database all of the specimens in the collection for 77 Rubus taxa. This is external.
Henry agrees (what else was he going to do...) and logs on to Specify. In prototype, this is Client only.
He goes to a menu item that says "Search Network" which presents several search boxes categorized by theme. Client UI Design
He chooses to search by taxon and types in Rubus. He is then presented with a list of taxa junior to Rubus and selects all the 77 taxa James requested and hits the submit button, hoping to have all network information available to him when he returns to the task.
Henry then switches to counting and identifying bugs stuck on sticky traps as part of his IPM duties. This is external.
A little later he returns to a message in Specify telling him that his request to the network has been completed.
Message: Notification. FP_Messages#FP_NOTIFICATON
Henry then retrieves a physical specimen folder from James' collection of specimens containing one of the taxa James was interested in. Henry goes to the specimen rapid data capture page he designed in Specify Client UI and types in the collector name followed by the collector number.
Message: Query, find sets given values for Darwin:Collector and Darwin:CollectorNumber FP_Messages#FP_FIND_SETS
A pop-up box Client UI appears with a list of records from the collector he input and a highlighted UI record containing the collector number he input.
Message: Query, given a set, get data for that set. FP_Messages#FP_GET_DATA
This should represent a duplicate of the specimen of interest.
?Requirement - set of duplicates provides single aggregate record and supporting individual records? (? does find sets get the summaries and get data get the details?)
With a click on the highlighted record he is presented with data that looks identical to the label data on his specimen. Client UI Design
The information presented looks enough like his physical label that he has no problem recognizing it. He then pushes a button that uploads the data into his capture form. Client
Henry laughs at how easy this job he just landed is and moves on to the next label.External...Use case meeting whiteboard image
On the next sheet, Henry types in the collector name and number an gets no match FP_Messages#FP_FIND_SETS. He then adds the date and a pop-up tells Henry that the collector does have records on the network that are related based on the date of collection FP_Messages#FP_INVENTORY. Henry browses the list FP_Messages#FP_FIND_SETS FP_Messages#FP_GET_DATA and realizes that one of the collections that has a number very similar to the one he is looking at appears to have the same location. Henry is over joyed because there is also a georeference which saves him the hassle of having to figure it out. He submits to the local database Client. In pushing the submit button, Henry hopes that his input makes it through quality control and does NOT appear on James's list of records that need to be reviewed Client.
A second scenario here is that the location data throws a flag indicting that the georeference does not match to some criterionClient or FP_Messages#FP_BUILD_SETS. Henry checks the georeference using Biogeomancer and maps the record and realizes that it is indeed correct Client OR Henry realizes that the georeference is incorrect and edits the georeference (and generates an annotation describing the correct georeference) FP_Messages#FP_CORRECTION_ASSERTION
Same as above for taxon name. Record's locality returned is identical but the identification is different. This is very likely a typographical error (which could be noted as a FP_Messages#FP_CORRECTION_ASSERTION). For older hand written labels this can be more problematic. Henry has difficulty discerning nasty handwriting and unfortunately only writes in two languages.
<PJM>Note the distinction between "I've looked at the image of your herbarium sheet, and you have a typographical error in transcribing the taxon name found in a determination on that sheet" FP_Messages#FP_CORRECTION_ASSERTION and "I'm a taxonomist and I have a new determination for you to apply to this specimen" FP_Messages#FP_NEW_DETERMINATION</PJM>