Use case lessons: Components of the SEEK architecture

Robert K. PeetUniversity of North Carolina

Infrastructure components - 1

• In each case could be distributed or centralized,

• In each case need initial data population [use case 3?]; need rules for population and task assignments,

• Can link to outside providers [use case 2]; need design specifications

Infrastructure - 2

1 Party • Registry with GUIDs [GUID assignments

in use case 5]• Use case 4 = registration and

level/rights of authority/expert

2 Reference • Registry with GUIDs• No agreed standard format yet –

perhaps EML format

Infrastructure - 33 Names• Registry with GUIDs • Separate spellings/renderings maintained??

[unique GUIDs ??]• Could be distributed over orgs like GBIF, IPNI,

ZooRecord• Current sources are not complete, not receptive to

additions, not supportive of spellings• Reference for source required (original concept?)• Support accumulating notes with dates and

parties?• Treat rank as attribute• Need agreement on treatment of alternative name

systems (English common, Spanish common, USDA codes, etc.)

Infrastructure - 4

4. Concepts• Registry with GUIDs• Combination of ref GUID & name GUID• Require party submitting?• Require date submitted?• Support accumulating notes with dates and parties ?• Optional additional fields for transfer schema

5. Relationships among concepts by party • Synonyms and acceptance [use case 1]• Components maintained by various authorities

Infrastructure - 5

6. Tools • Submission• Annotation• Dataset markup• Access to registries

Taxonomic workflow - 1

1. Tool for searching for related concepts for researching a taxon.

• May need to limit scope to a particular perspective [use case 3 = select preferred view; use case 4 = display concepts associated with name; use case 9 = display concepts associated with different information sources such as reference or specimens; use case = 10 display details about a concept; use case 7= trace history of chances in concept; new use case = find GUID]

Taxonomic workflow - 2

2. Tool for submission of Parties, References, Names, & Concepts

• Need business rules for who can do this – is it open?

• Use case 11= enter existing concepts from published references.

• Use case 12 = enter correlations from published references.

• Use case 13 = enter informal concepts [e.g., draft taxa. Need business rules]

Taxonomic workflow - 3

3. Tool for managing authority perspectives

• Use case 14 = acquire synonymy from expert or authority

4. Tool for submitting new perspective to authority for peer review / approval

Ecology workflow - 1

1. Tool for ecological dataset or publication markup

• Highlight taxa in dataset for systematic review• Choose preferred authority (e.g., ITIS 2004) • Each taxon for review comes up once in a

form:- List of candidate concepts, most likely

first- If not on list, but well formed concept- If not on list and not well formed

Ecology workflow - 2List of candidate concepts, with most likely listed first:• Entries show name by selected authority: accepted name,

concept name, concept reference, GUID.• Option to expand list to candidates not on authority

preferred list.• Enter note if any.

If not on list but well formed concept:• Search for Name; if none new form for entry; GUID assigned.• Search for Ref; if none new form for entry; GUID assigned.• Enter note if any.

If not on list and not well formed:• Enter one or more correlations with well-formed concepts.• Enter dataset-specific name.• Enter note if any.

Ecology workflow - 32. Tool for ecological dataset or publication

annotation• Select dataset or publication• Annotation probably gets appended to dataset

Form • Enter Party making annotation by GUID (GUID

includes name & affiliation]• Enter date of annotation.• Enter notes if any.• Enter taxon name [GUID] in dataset being

annotated• For new concept complete form as above.

Search workflow

Tool for searching for related concepts for developing search criteria or researching a taxon

May need to limit scope to a particular perspective [use case 3 = select preferred view; use case 4 = display concepts associated with name; use case 9 = display concepts associated with different information sources such as reference or specimens]