Agenda

• General thoughts

• Personas tune up

  • state of the document

  • proposed final personas

  • feedback

• Vision and scope

  • Importance of PCDM on wireframes

    • single file work

    • multi-file work

  • Plan of attack

    • basic actions

    • non-expert or infrequent users

• Next Meeting is Dec. 4.

Resources

• Google Hangout via Columbia University

• Proto-personas

• Persona Scratch Pad (Google Doc)

• Personas v2 (Google Doc)

Notes

Attendance

• Sonya Betz (University of Alberta)

• Anna Headley (Chemical Heritage Foundation)

• Sue Richeson (University of Virginia)

• Ellen Ramsey (University of Virginia)

• Simone Sacchi (Columbia University)

• Michael Tribone (Penn State)

• David Trujillo (University of California San Diego)

• Gary Geisler (Stanford University)

• Hui Zhang (Oregon State University)

Personas

Researcher/Professor

• question about "links to different works" and whether or not this is to accommodate links within the system or outside of the system. General intention that it would link to other objects within the system. However, a file could be uploaded into the system as part of a work that lists works outside of the system.

• ways to pull information from other sources would be a time saver for this persona. ORCID, DOI, etc. The effort to upload and add metadata is at times a barrier.

• the UI should be simple to accommodate this persona

• tends to be a lack of awareness about IR and its uses.

• copyright restrictions tend to be problematic for this persona when uploading work

• versioning an important part of the persona for things like software and data sets

• statistics about work(s) important; views, downloads, etc.

Research Assistant (previously Grad Student)

• same basic needs/goals as researcher

• ETDs are out-of-scope for Sufia UI and require different workflow and approval process

• works on behalf of a researcher

• bulk upload to be addressed in tech persona

• could use a little more work

Repository Tech (previously Proxy)

• minimal metadata

• assigned as a proxy by librarian, cataloger, etc

• participates in a project

• not in cataloging 

• high volume

• not a content expert

• sometimes each upload needs to be evaluated individually

• cataloger has metadata expertise

• regular user

• not a first timer

• tech gets it "up there"

Homework

1. Personas (These are to be used as a lens when reviewing the PCDM wireframes that Lynette has provided to the community.)

2. Creating Works and Uploading files - workflow and/or wireframes (Use these wireframes and actions as a stepping stone to designing interactions based on the broader PCDM goals through the lens of our personas.)