• V2Inspector2Todo

V2 Inspector2 To Do

V2Master | V2Inspector2Specification

Strategy

• Our current goal is to get a reliable prototype with all the features required for production use,

  • including the ability to customize, via configuration (not programming) the data fields in the tags and scans tables

Conversion from SQLite to PouchDB

1. See: V2Inspector2Synchronization

Features Required

1. Client-side
   • Login
   • List Sorting
   • Improved lists
   • Usability improvements
2. Server-side (Via an angular app?)
   • Dashboard prototype
   • Report prototype

   • Login & user roles

   • Audit trail
   • Record versioning
3. Stress testing

4. Documentation & Method Statements

Future features

1. Flexible fields in forms. E.g. generic fields in tags & scans

2. Voice recordings
3. Video recordings

Development

Bugs and Incomplete Features

1. Photos:

   1. Photo detail: Does not display date, file name, image type or size

   2. New photo
   3. Delete photo
   4. Dispatch to photo viewer from photo detail page
2. Infinite scrolling of:

   1. Tag list

   2. Scan list
   3. Photo list
3. Sorting of:

   1. Tag list

   2. Scan list
   3. Photo list
4. Ability to detect and resolve conflict records
   1. Tags
   2. Scans

5. Get Search for Scan Code working again

6. Display (8-digit hex) IDs in detail page headers

7. Implement user authentication & transaction authorization

   1. What is possible with CouchDB?

8. Bug: Sometimes you get a Are you sure you want exit Inspector? dialog when you shouldn't

9. Test for design document conflicts when two different devices upload design documents

10. Review code and make sure no local DB fields are being used

Performance and Reliability Testing

1. Reliability and tuning of server synchronization:
   1. Initial DB download
      1. Via fast wifi
      2. Via slow GSM with occasional network interruptions
   2. Upload of lots of new photos
      1. Via fast wifi
      2. Via slow GSM with occasional network interruptions

2. For testing & diagnostics: Implement an attachment logging function that shows all attachments and their sizes

Usability Improvements

1. Cleanup display of tag list
2. Cleanup display of scan list

Server Updates

1. Decide how to implement a desktop app
2. Implement record versioning?
3. Implement audit trail
4. Implement prototype dashboard
5. Implement prototype report
6. Implement to ensure that tag.tag_value is unique (implement in app too?)

7. Implement user roles

   • Administrator - Able to manage users & user roles

   • Normal User - read/write access

   • Observer - read access only

8. Implement transaction protection based on user roles

9. Implement user role administration

10. Implement record versioning

Unimplemented Use Cases

1. Delete non-uploaded records on the client

   • Photos

   • Scans - Only if no photos?

   • Tags - Only if no scans?

2. Handling items deleted on server
3. Dealing with record conflicts
   • On server
   • On client
4. Use case: Replace a tag with a tag with a different scan code
   • Implement a tag_id in the scan record?

Testing

1. Download
   • Records loaded
   • Photos loaded
2. Upload
   • Records uploaded
3. New scan item
   • Looks OK in list
   • Detail
   • Dates OK