Discussion: Duplicate Finding Find_Duplicates. Identify targets for native data entry applications into which we will embed duplicate finding functionality.
Revised InvertENet FP budget, budget justification, and supporting docs went to Kristin, updated to current numbers, and then have gone to Petra all staged ready to go when submission process reopens.
More UI extraction for the driver. Also built an occurrence index and a botanist index for Solr/Lucene based on HUH data.
Paul: Budget and justification and supporting paperwork ready and circulated to Petra.
Maureen: Kansas has a separate jar for SGR, just querying a lucine index on a copy of the gbif Cache. Chuck has copy of GBIF cache ready for query. David: Camel will alow us to replace Triage/JobPlanner/JobRunner with configurable routes for messages within the system. Camel can provide a message bus that is slightly lighterweight than an enterprise service bus.
Tianhong: Have actor and service for date internal consistency within record. (Problems 1,7,8 from James' list). Use ISO 8601 as intermediate format? i.e. YYYY-MM-DD Bertram: Also trying to set up a high level modeling language for describing curation workflows (in a research direction). Bertram: Overview of curation workflow in a new conceptual model/language on agenda for Friday. Tianhong: Will send out some further questions on email.
On table with Kansas (Jim Beach): Using Species Analyst services for occurrence QC. We have an occurrence with a taxon name and a georeference: what would we like in a service to check if this occurrence is an outlier for a species distribution model for this species?
Paul: We provide a taxon and georeference (from an actor in a workflow), they provide a service that asserts whether this fits inside a predicted species distribution or not. Bob: Does it matter if they have environmental layers pertaining to the date collected? James: Probably, yes. Question worth asking. Paul: Something to pursue with Kansas? James: Yes, if not too much work.
David: Sven suggested that we keep count of how many people express an interest that covers some record, and/or a count of how many times a query has requested some annotation. Maureen: Problem to be solved? Only run a QC analysis a record once in a certain timeline: Chuck: Prioritizing records to be fixed. Older records will be weighted more heavily than newer records, as more queries will have been launched, may need to compensate for that. Bob: Formulate sparql query. James: Prioritization should come from person who asked the question - perhaps allow users to flag records as having priorities. Also have human intervention needed workflows, might have priority there. Paul: We need to start from the UI researchers use to obtain data: David: Query and Analysis jobs similar. Could create triples and associate with fedora PIDs. Paul: Something to start on as soon as David has the message driven architecture in place.
Maureen: need a FP message to provide harvests for the network. David: Will make job and messge type for this. Maureen: Harvester/processing code lives in network, can call up a provider directly, or can be given a harvest from a provider that got wrapped up in a FP message and handed to an access point.
For friday and next week.
David: Need to add transcribing annotation when data is coming from image. Added support for transcribing motivation to message generation, not yet plugged into symbiota. Nico -- wondering if David Lowery can visit Ed/myself at ASU before end of year for a 2-3 days SCAN/FP user interface optimization session. Could talk about options while at TDWG. Jim: Paul give Nico a call and figure out details of what he's looking for.
Maureen: Haven't picked a date yet.
Maureen: Still working on refactoring using workbench backend.
This page was last modified on 16 October 2013, at 19:26.