Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

What about UX and accessibility?



Meeting notes:

Complete UI Interactions documents - We will produce two documents:

UI Interactions = Call it "Hyrax Feature Guide"

UI Testing Tracking = Call it "Release testing template" and make a new version of it with every release. 


Complete Hyrax Feature Guide document - for Hyrax 2.0 -

  • How do we do this before sandbox? 

-Decide and Audience

...

  • Decide Audience: -We want to make this a manual that explains all the features, and admin. 
  • 1.3. walkthrough - Chris (mark features that are not in 1.3, add missing interactions) by Sept 1st. 

-We want to make this a manual that explains all the features, and admin. 

...

  • Regarding Format: categories seem good, the repeating the

...

  • word interaction is distraction.

...

  • Needs more examples, that address "Use this for" examples. Ask Steve what he has in mind.
  • What is in Hyrax 2 and when can we get a list.  


Release Testing Process Notes: 

  • Need bug reporting template. 
  • What is a time frame that is acceptable for returning results of test? (2-3 weeks) 
  • The turn around time for updating the 2 important documents is of concern. 
  • We think we need 3 institutions to commit to this work for each release ahead of time. Would be good to rotate these institutions. 
  • We would love for 2 institutions to commit to upgrading in-production system systems before wide-release but realize this is hard. 
  • Minor release should have less process? 
    • update the 2 documentdocuments
    • new features should be tested
    • how thoroughly do all features need to be tested? 
  • Accessibility

...

  • testing should be included in tab, but needs some expertise. What is the minimal that we support? Should automated testing be done as a minimal, consult with Michael and

...

  • Kate

...

  • What is in Hyrax 2 and when can we get a list.  





Before the testing tracking document Before the Release Testing Template is complete, we need to complete UI interaction and answer these questions

...


    • What browsers and platforms should be included, what are supported? Poll repo-managers at least. 
      • End User tools
        • OS
          • Windows 7 + 
          • OS10 
          • Mobile platforms for what? Would it hold up a release? 
            • Android version? 
            • IOS version? 
      • Admin and staff tools
        • OS
          • Window 7 +
          • OS10?
          • Mobile not needed
      • Chrome, Safari, Firefox, IE, Edge (for end users), Opera (for end users?), mobile browsers (for end users?)






To do's: by Aug 18th

Ask repo-managers what platforms and OS should be tested/supported

...