Ecabinet

Attachment is Task List chart.

Input:
Parent docx + pdf + child docx : 3 docs with one filing number (simulates the current Add Document screen). 
-- Filing into an existing case.
-- No confidential data in docs (ignore Rule 6 questions)
-- Do we care about “number of pages”?

1/15/13 RC: Rao sent a number of fixes listed as "Status Ready for Test", see attachment "2013-01-15 Thru 1-9..." below.  Cindy and I tested, all OK that were marked Ready.

1/11/13 RC: sent my parent document to Cindy, ready to use this for 1/14 testing.  see doc starting "2013-01-11 ..."

1/11/13 RC: talked through consolidated email (attached below, see emails starting  "2013-01-11 ...") on this morning's call.  New drop scheduled for Mon morning, 1/14/13. 

1/4/13 RC: From email from last night (also see attachment "2013-01-04 StatusCallNotesAndResolutions", same as items below): There are filings in “Rutland Civil” in Test for you to look at:
a. 30831 and 30833 were tests where we had previously submitted a filing with the SAME root name:   XXX_0.docx, XXX_1.pdf, and XXX_2.docx.  When you file the second time, the system doubles each document – so a parent and 2 children become 6 documents, each “phantom” is of type Misc, Unknown.
b. This happens even if you file 2 parents with the SAME file name, (30836 and 30837), each gets a phantom 2nd doc in their filing
c. If you put a file into U:QuickFile without the appropriate naming convention (not in format: xxx _#.ext; look for _#. ??) it disappears and nothing happens, not sure if this is what we want.  Perhaps good to attach it to an email, subject “Unknown file submitted to QuickFile” and send to the sys admins that are checked.  RESOLUTION:  Rao's file watcher will do a 2-pass process, pass 1 to pick up all files following naming convention, pass 2 to pick up any other files and attach to email to Admins with Subject: Unknown file submitted to QuickFile.
d. Please change the text on the “default document image” you generate.   Should just say:  Please select the “View Original” link above to display the original document.
e. When the only thing wrong in an XML parent is the ERN number, you accept the filing and the filer is “Unknown Filer”.  No error message is sent to the system admins.   Is this what you intended?   QUESTION:  Will it be possible for us to correct this to a known filer?  (Answer: No.) RESOLUTION: If ERN is unknown, Filing will be sent to Admin (with attach of parent) with message to correct ERN and resubmit filing.
f. drop-downs for Doc Category and Doc Type come up fine on the Parent when first opening the filing.  But, if you go Next and Prev, they disapper.   In addition, Document 3, also a Smart Doc with XML, the Doc Cat and Type do not appear.

g.  “eventnumber” should only fill in from the Parent – same as Docket Number.   On all further docs in the filing please just carry forward eventnumber.   This means, I think, that you only grab  Docket Number, Event Number, ERN/Filer from the Parent.   And then these three fields are ignored on other Smart xml documents in the filing (you are doing that now, I notice, with Docket Number and ERN/filer, they seemed to carry forward on Doc 3 of my test with the setting from the Parent – this is correct).

h.) ADD new System Admin checkbox for all User registration records (only available on the Sys Admin screen) to control send/don't send of "email1 and email2".  Checkbox label will say:  SUPPRESS SENDING EMAIL1/2.   If checked, the system will not send email1/email2.  Default is box is not checked, which means the system will send the emails normally.  This will apply to both QuickFile and Online filing.

 

12/27/12 Rao - See Email from  last Friday regarding file naming conventions. Also changed review screen so that when parent (i.e first document ) is accepted all children are also accepted. Same with rejection. Also can't modify the children during review process.  Document group/type for the children is derived from document if document is a smart document or from file extension.

 

12/14/12 CF: Three docs placed in Quickfile location, two docx and one pdf. 

- error 1: Both docx's successfully transmitted to eCab but the pdf did not

- error 2: no error message was received about the pdf (note: more about error message in 1.1)

- error 3: Each docx created its own filing number: all three docs should have been in one filing number.

12/14/12 RMC:  Per status call this morning - Rao agreed that we should have functionality that, if we submit a "filing" with multiple docx documents THAT HAVE XML DATA in them, that the "parent" (first) docx will have unit/div/docket number but that the new file watcher would fill in the doc category/doc type (and copy forward the docket number from parent) for EACH of the children documents.  Rao asked that I add this note into sharepoint.

12/7/12 RMC (9am): on status call Rao said he would look at what is going wrong and we will have another status call update at 3pm today.

12/6/12 RMC/CF: Rao – you will see in \.68\efile\TEST as “Rick1.docx” document (attached).   We took: your sample1 (with the new tags), put in my ERN, our docket number, took out the extra tags for now (e.g., case type and stuff in the body).  Then copied Rick1.docx to U:quickfile.   Successfully tranfered out to \efile\TEST where it now sits -- Then nothing??   Don’t see where it got into eCab.

12/05 Rao - Deployed to test insatnce 159.105.17.4.  Watcher looks for files in folder \\10.226.20.68\efile\TEST

Test 1.2 applies (1.3 too?) +
1) See if Parent+paperclip documents show up properly in Clerk Review and Clerk/Judge Viewer
Input:
Parent docx + “confidential list” docx

12/6/12 RMC:  Nope, Exhibit B specifically references "paperclip documents".  Please suggest to us what you need.

12/05/12 Rao - Marking as Partial because if i remember correctly  assumption is that this interface does not support paperclip (parent + child ) documents. If assumption is not correct need to discuss naming convention of content control tag that can be used to create the link

Test 1.1 – 1.5 apply. +
1)  Test “what ifs” – e.g., one or more fields are missing
2) Test what happens if there are Handling Instructions (how do we input these)
3) What if we put in Plaintiff and Defendant – how will it recognize these and will it construct a Case Title?
4) What if docket number is missing?
5) What if docket number is not an electronic case?
Input:
Various XML documents with various XML fields
-- Parent “docx” of various types
-- Filing into an existing case

12/27/12 Rao - See Email from  last Friday regarding file naming conventions. Also changed review screen so that when parent (i.e first document ) is accepted all children are also accepted. Same with rejection. Also can't modify the children during review process.  Document group/type for the children is derived from document if document is a smart document or from file extension.

12/6/12 RMC:  Without 1.1 - 1.5 fully working, this test is not ready for Jud Testing.

12/05/2012 - Copied Sample documents i tested with to folder \\10.226.20.68\efile\TEST\VTTestSamples. For importer to map information correctly , content control tags must match known Property names.  Recognised content control tags are

 

Organization (AKA Unit)
Division (Example Civil , Family)
casenumber (AKA Docket Numer)
CaseTitle
DocumentGroup
DocumentType
ERN

case (upper/lower) of tag does not matter. Space does matter

After 2.2 above: +
1) Can a “new case parent document” start a new case and bypass clerk review at the same time?  If so, need to enter case title in document.
2) Configure system via System Admin screen to indicate which doc types (and/or doc categories) are allowed to start “new cases” if XML docket number not already in the system? (e.g., we would not want a “DCF Case Plan” to automatically start a new case in eCabinet.)
Input:
“New case” parent document: XML docket number not in system, starts a new case.
May have other documents in filing: docx + pdf
-- New case documents start case directly if allowed (can bypass Clerk Review)

12/6/12 RMC:  Needs prior tests to work before testing this, especially 2.1.

3.1 above for new search and TOC features +
1) Test viewing the pdf version of a document.   Then “unhide” its original.  Save original with another name.
2) TOC screen can show one row per document.  Additional TOC screen capability to call up original without going to “view doc” screen (“view doc” would show the pdf version).
3) What happens if the document is a new type (e.g., xlsx).?   Does the TOC screen have a new column that indicates document format?

12/05/12 Rao - marking as Being developed as Logic to retrieve original is not working correctly

ID type drop down is not consistent (see attachments).  Also, if you change the drop down value it creates duplicate records.

1) Add a "Comment" field to the System Admin version of the Registration screen so the system administrator can add notes.

2) Add a new field to Registration:  "Date Email Exemption Expires", if date is filled in, and in future, the Registration has been granted an exemption from receiving notifications via email.

3) Allow System Admin screen to change "Role" for any Unaffiliated User.  (Display drop down)

4) Display user's Security Question and Security Answer on the system admin version of the Registration screen only.

5) Review design of Registration screen with Michael.

In addition to logging emails sent from the "email link" (Clerk Viewer, Judge Viewer, Clerk Review) to each person selected in To: link (and/or to the Filer), we would like to have the email logged into the CASE, so that a clerk/judge could see every email on the case TOC screen.

Please remove the "VT" from the VT Employee ID number.  The entry should read Employee ID Number.  (to minimize possible error when one enters a "v" in the field and the default populates as Vermont License Number.

See Attachment for discrepancies on screens.  Since we only use Attorney license @ and employee ID number, please remove CMS USer ID, drivers license and SSN.  Leave the "other in place please.

see Attached.

11/14/12 RMC:  Giuseppe said that AmCad will fix these for us until next drop, since this defect only shows up occasionally when a mistake is made.
11/13/12 CF:  Further information - when I attempt to change the ID type and save the modification (popup says indicates the save was successful, but it is not)  it appears a duplicate entity is created.  See attachment "duplicate ID".

11/8/12 RMC:  Giuseppe thinks this may be a defect in the system.

Please make all fields except email alternates 1 and 2 REQUIRED on both the registration screen and the user edit screen for MY PROFILE.  (DO NOT make these changes to the  system admin MANAGE USERS screen.) Goal is for eCabinet to eventually be THE directory for all this information.

Have a system message that generates the “temp password” to not be “eportal”, but to be something more “random”.   Can be a simple formula.  Decision is to use  like the second (small case) and third (capital) chars of last name plus the numbers in the current date mmddyy.  (e.g., Foster reset today Temp Password = oS120512).     

Remove the “activate link” email message, so they only get two email messages:  1) “We have received your registration question, we will review it and you will get another email when your account is activated”  and (2) Your eCabinet account is “active” and the rest of the text about they should go into Account/MyProfile to set other emails, change email, etc etc.”   This assumes that we manually activate all registrations.

My profile page requires phone format containing dashes.  Format on admin's "Manage Users" screen has area code in parens, no dashes. Entering dashes causes the number to be incorrectly displayed.

See attachment of screenshots.

In WorkQueue listing, right column "Received Date".  If you click the col header for decending it sort (little down triangle).  But if you click for ascending (little up triangle), triangle appears in col header but nothing happens.

1) Always Case Name, not Case Title.

2) Always Doc Group, Not Doc Category.  Decision: should we change to Doc Type, Doc Subtype (like Case?)

3) Standardize buttons, e.g., Cancel always in middle.

4) Standardize common blue link placement, esp.  Refresh and Close at right side of menu bar

5) Remove extra "ok dialog boxes", e.g., no box after clicking Return on Clerk Review; but perhaps a box when click Close reminding that you are keeping the filing under your name.

6) Implement short queue names in left tree

7) Cleanup in System Admin screens (see documentation?)

8) Routine to delete out "orphan filings" - when they had to create a fake Accept to reject something and gave it a bogus docket number.  (Need format for bogus docket numbers.)

9)