use cases / requirements notes from 6/12/2007 rockville, md meeting

11
Use Cases / Requirements Notes from 6/12/2007 Rockville, MD meeting

Upload: amie-greer

Post on 05-Jan-2016

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Use Cases / Requirements Notes from 6/12/2007 Rockville, MD meeting

Use Cases / Requirements

Notes from 6/12/2007 Rockville, MD meeting

Page 2: Use Cases / Requirements Notes from 6/12/2007 Rockville, MD meeting

Frank Hartel (1)

• User Identification– Expertise– Domain Rights Assignment– Registration– Validation

• Targeted locks• Blocks of Concepts (Harvest blocks, no

individual)– What is the criterion for creating a block?

• Hierarchical authority

Page 3: Use Cases / Requirements Notes from 6/12/2007 Rockville, MD meeting

Frank Hartel (2)

• Lead can mark concept as “Ready”• Status of concept (in Progress, not started, etc)• Add Concepts and tree them – Form• Modify concepts and tree changes – Form• Suggest New Class property, annotation, type,

etc. - Form• Report of History of concept – format and dialog• Restore Wiki if Corrupted• WYSWYG Editing/Ajax completion support• Voting support – to resolve contention.

Page 4: Use Cases / Requirements Notes from 6/12/2007 Rockville, MD meeting

Frank Hartel (3)

• Karma, WikiPedia & good/bad behavior

• Voting for contributor by users and other contributors

• Wiki to Protégé

Page 5: Use Cases / Requirements Notes from 6/12/2007 Rockville, MD meeting

Frank Hartel (4)

• Wiki Is Public– Register saying who you are, how to get a hold of

you, bio– Indicate which domains you want to be able to edit– NCI provides logon identity, including rights for

domain• Assignment – everyone starts out as contributor, one of them

morphs into lead.• “Lead” – can change the state of a review process to

complete– Weekly – “harvest” complete records, run through

export and put into Protégé as part of workflow– Concepts marked as complete are locked – no further

work can occur

Page 6: Use Cases / Requirements Notes from 6/12/2007 Rockville, MD meeting

Hartel/Chute

• Annotations in WIKI are wholesale imported into corresponding annotation space in Protégé– Need to test whether history can live independent of

the terminology (Collaborative Protégé)

• Annotations are assigned status within Protégé• Re-import through back-end repository will carry

modified annotations into wiki.

Page 7: Use Cases / Requirements Notes from 6/12/2007 Rockville, MD meeting

Chris Chute

• Hierarchical Authority

• Federated namespaces– Namespace– Wiki

• Some dialogs need to be off limits (e.g. dialog about competence/etc. of )– Notion of restricted meta discussion

Page 8: Use Cases / Requirements Notes from 6/12/2007 Rockville, MD meeting

Gilberto Fragossio

• Change history of concept

• Discussion history as part of collaboration

• Needs to be accessible in Wiki

Page 9: Use Cases / Requirements Notes from 6/12/2007 Rockville, MD meeting

Secondary Requirements

• Ability to lock for off-wiki edits

• Ability to record version that was being seen when the editing occurred– Ability to detect/flag out of date edits– Ability to uniquely identify edits for export and

import

• Wiki export (english + (?template? ?RDF?))

Page 10: Use Cases / Requirements Notes from 6/12/2007 Rockville, MD meeting

Secondary

• Figure out how Wikipedia manages authority structure

• Investigate talk pages

• Flesh out domains in NCI Thesaurus– Start w/ Kinds as first approximation– Parsia (Hendler’s group) – topological

grouping (e-connections)– Appeared to be congruent w/ Kinds

Page 11: Use Cases / Requirements Notes from 6/12/2007 Rockville, MD meeting

Issues

• How much writing within the wiki itself?