combination of SNART 50 and SNART 51, count is 16 update sets (really 15); 2013/02/22 - 2 should not be in the list.
2013/01/17 - 3
previewed with two errors, changed them to commit. Committed the set.
2013/01/29 - 1
one error, changed it to commit. Committed the set.
2013/01/29 - 2
two warnings, two errors. Reviewed and changed to commit. Committed the set.
2013/01/31 - 1
one warning. Committed the set.
2013/02/01 - 2
one warning. Committed the set.
2013/02/04 - 4
one warning. Committed the set.
2013/02/04 - 5
one warning. Committed the set.
2013/02/04 - 6
two warnings. Committed the set.
2013/02/05 - 1
one warning. Committed the set.
2013/02/15 - 1
two errors, changed them to commit. Committed the set.
2013/02/20 - 1
one error, changed it to commit. Committed the set.
2013/02/21 - 3
one error, changed it to commit. Committed the set.
2013/03/01 - 1
42 errors, changed to commit. Committed the set.
2013/03/08 - 1
63 errors, changed to commit. Committed the set.
2013/03/08 - 5
4 errors, two of which are collisions. The collisions should not be advanced. The other errors should be advanced. Committed the set, and confirmed I wanted to skip two of the changes.
2013/03/14 - 2
no errors, no warnings. Committed the set.
...
All variables have a length limit. TASK has a limit of three.
The initial PTAEO should work the same as the recurring PTAEO. The only difference is the labels. In many cases we will need to collect two PTAEOs on the same catalog item.
Requirement 51:
This requirement is even less visible than requirement 50. This scope consists of all the server side supporting technology which allows the requirement 50 technology to speak to Yale web services. If the scripts are getting a return from the web services saying the ptaeo is valid or invalid, that is a validation of requirement 50.