My favorites | Sign in
Project Home Downloads Wiki Issues Source
Search
for
UserStories  
User Tasks and Application Requirements.
Updated Jul 28, 2009 by akwer...@gmail.com

Starting the application
The application will begin by bringing up all the icons representing families in the corpus and displaying them as an image collection. A pull-down list allows users to select different input (data) files for the visualization.

Running the application
Users can filter the visualizations by role (principal, witness) or transaction type (prebend, land).

Milestone 0

Application Interface - accessing and working with data input files

A user can:
1. see a graph visualization for a selected input file
2. modify the visualization layout to explore the data
3. browse through the individual nodes/edges properties
4. update the properties of a given edge/node selection
5. apply filters to the resulting output graph

Legend
Distances between nodes represent the strength of a relation (clan affiliation or transaction occurrence).
Colors of the edges represent the type of a relation, with an optional label indicating the sub-type as needed.
In the future, users can filter the visualization layout of people by selecting or de-selecting relation or transaction role types.

Milestone 1

Person-Centered View - creating and updating individual person records

Users can: 1. get a representation of the relations currently defined for a selected individual
2. access a list of the people in a corpus and browse the graphs for each individual
3. Users can update individual entries by adding, editing or deleting db records.

Later Milestones

Document-Centered View
Under this view, users can browse through all the documents in a given corpus and get an individual representation of all the names for the one(s) they select. (Note: In the future, users can save changes to a personal workspace on the server). Custom changes are marked and annotated as a comment below the graph.

Users are given a representation of the transaction-network in the chosen tablet, displaying individuals as nodes highlighted by role and seal (on mouse-over). Users can navigate the edges of the resulting distributed tree graph to see transaction information. Individuals are grouped in the graph by transaction, with all principals closer to the center of the tablet (center node). Each principal node is the root of its own transaction group sub-tree, connecting individual participants by role.

Family-Centered View
Displays of related individuals indicating their connection in a rooted tree view (not including spousal relations). Nodes hold information about individuals, including links to their person view and various tablet views. Users can select individuals at start up by clicking a name in the pull-down list or linking via an image in the alphabetically sorted collection of family/clan seals. Colored circles below nodes represent the type of transaction including role counts (on mouse-over). On click, the circle opens the tablet-centered view for this transaction.

Users can update a family, individual or transaction using the family management form. A filter of transactions allows users to select only those family members who have engaged in a similar type of transaction. In the future, users can make changes by adding/dropping nodes on the visualization.

Service Stories

We would ideally include services stories for each user story, but have not gotten that far with documentation. However, service stories are captured on the Services Planning page. In addition, the Services Architecture notes include similar descriptions.

Comment by project member lpea...@berkeley.edu, Jul 13, 2009

Pierre/Patrick: Does "Users" mean all users or does is, in various parts of this documentation, mean the team-members? I'm wondering, for example, about #3 in the person-centered view, and the integrity of the corpus if all users can make such changes.

re: Starting the application The application begins by bringing up all the clan seals representing families in the corpus and displaying them as a collection of images.

If I understand this sentence correctly, it is meaningless in the context of the text and seal-impression corpora. There is no such thing as a "clan seal". If however, you suggest having an icon or avatar for each family, then we could rephrase the sentence appropriately.

Comment by project member lpea...@berkeley.edu, Jul 13, 2009

This all seems to make sense based on the discussion and preview we shared on June 24.


Sign in to add a comment
Powered by Google Project Hosting