Master ToDo List

General Items

1. Complete and prioritize this todo list
2. Order business cards for Tibor and Martin Pike.
   1. Find and send layout PDF to Tibor (AH)

3. Order PC & Excel books for Edina (AH)

4. Review Coya document coding scheme sent by Geraud
5. Clarify MWSt. for Tibor invoice with accountant
6. Complete DrawMGT documentation wiki
   • Add all images
   • Improve internal linking
   • Update for latest version (which version?)
7. Implement Wiki for NDD project
8. Implement integration DrawMGT and Wiki software (unified login)

MET ToDo Items

1. Finialize file and metadata transfer procedures and formats with Martin Smith
   1. Document metadata file format in Wiki (and make sure Martin Smith agrees)
2. Document plan for next activities we perform for Martin Smith
   • Should have own wiki page
3. Setup hosting of Budapest server (TN)
   • Select provider
   • Strategy for partitions: encrypted/non-encrypted
   • Access for Edina/Martin for file transfer
   • Encrypted backups

NOK ToDo Items

The items refer to Martin Gmür's spreadsheet.

1. Items to clarify with Martin Gmür:
   • Item 4.2: Probably can be closed. Fixed by having a single layout for documents.

   • Item 11.3: Unclear: Schaltfläche mit Prozessschritten unbennen (translation related)

2. Software updates:
   1. New document: Drawing code entry (the vertical list of input fields): Display drawing component names (via tags) to left of select lists (item 2.7, easy)
   2. New document: Custom template to hide display of layout type and document type input (item 2.1)
   3. New document: Automatically determine next sequence number, given the rest of the document code (item 2.9, difficult)

   4. New document: Set classification fields button, works like Preview but stays in input form (item 2.13)

   5. New document: Custom input template that highlights classification fields that are part of the drawing code
   6. New document: Suppress display of '*' for optional document code components

      • will probably have to implement a new drawing code keyword optional that is used to set non-required for the component field.

   7. New document: Drawing code config for part (Teil), make alpha numeric, instead of numeric. (item 2.12)
      • Change field type of sheet number to alpha-numeric?
   8. Revision file upload: (item 2.12)
      • Display expected file basename in initial screen
      • Add checkbox that enables automatic renaming of uploaded file to conform to naming convention.
   9. New comment: Add ability to add/remove subscribers when the comment is created
   10. Generate an email when a revision is rejected (how? to whom?)
   11. Implement additional document search fields:
       1. Dates for planned workflow steps
       2. Initials for workflow steps

   12. Implement my document workflow todo. E.g. list of revisions where I have to perform a workflow step

       • Only revisions assigned to me
       • Ordered by plan date
       • Includes only revisions where the completed date is not set
3. Software updates that require a data model change:
   1. Implement new public/private field: 3-date flag to make public to contract or system (item 3.13)
      • Could have performance implications

      • Could make it difficult to know when to display [view] links

   2. Implement record versioning, to allow a field level audit trail
   3. Implement file versioning, to allow overwritten upload files to be recovered
      • Will have consequences to storage and backup
      • Older versions may only be available from backup
4. Reference data and drawing code configuration:
   1. New task types:

      • Ablehnung - To document why a revision was rejected

   2. New revision types:

      • Vorabzug

   3. Temporarily delete top-level classification records (e.g. records with code X00 or X0). This is being done because searching for, for example, Objekt 100 - Fremdanlagen will not include the '1XX' Objekten. Classification fields affected:

      1. Kontakt
      2. Objekt
      3. Dokumenttyp
   4. Add new approval status: Approved (Over-ruled)
      • Allows Release/Transmission of a revision that has been rejected.
      • The over-rule applies to the previous workstep
   5. Change revision numbering from 'v00' either: (Requires input from Axpo/GMM)
      • A, B, C, ... followed by 1, 2, 3, ...
      • 1, 2, 3, ... followed by A, B, C, ...
5. Site settings:
   1. Documents: Set all classification fields that are mapped from the drawing code required
6. Complete translation of reference data:
   1. Comment types
7. Translation

   1. Main menu: Rename Submittal (in DE) as Versand

      • What names to use in EN version?
   2. Input fields names in task search
8. Classification attributes:
   1. Fachgebiet is dependent on Fachgebiet. Solve with V12.x. (item 3.3)
9. Deployment: Goal is DrawMGT deployment by end Nov (excluding Wiki)
   1. Prepare configuration on lu.softxs.ch for ssh tunnel
      1. Test ssh tunnel
      2. Negotiate procedure with Axpo Unix specialist (Jörg Leppin) for getting access
         1. Alway available
         2. On demand via email/telephone
         3. crontab
   2. Ensure all required tools available
      1. MySQL
      2. PHP - including MySQL access
      3. Apache - including support for PHP5
      4. htmldoc
      5. Perl and PHP extensions
   3. Outgoing email configuration
   4. Apache configuration
   5. php.ini configuration
      1. For Apache
      2. For PHP called from command line (may be a different php.ini file!)
   6. Test DrawMGT installation