Master ToDo List
Contents
General Items
- Complete and prioritize this todo list
- Order business cards for Tibor and Martin Pike.
- Find and send layout PDF to Tibor (AH)
Order PC & Excel books for Edina (AH)
- Review Coya document coding scheme sent by Geraud
- Clarify MWSt. for Tibor invoice with accountant
- Implement Wiki for NDD project
- Implement integration DrawMGT and Wiki software (unified login)
General DrawMGT Development Tasks
- Update V11.3 data model (drawmgt.PDM) to match current schema
- Migrate recent V11.3 updates into CVS leading edge
- Identify any high-priority bugs/updates:
- V11.3 - Mainly NOK requests (see below)
- V12.0 - Anything required by Martin Smith
- Update V12.0 data model (drawmgt.PDM) to match current schema
- Declare V12.1 branch for multi-classification
- Determine priority (Martin Smith)
- Document proposed design and data model changes
- Complete DrawMGT user documentation wiki
- Add all images
- Improve internal linking
- Update for latest version (which version?)
MET ToDo Items
- Finialize file and metadata transfer procedures and formats with Martin Smith
- Document metadata file format in Wiki (and make sure Martin Smith agrees)
- Document plan for next activities we perform for Martin Smith
- Should have own wiki page
- 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.
- 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)
- Software updates:
- 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)
- New document: Custom template to hide display of layout type and document type input (item 2.1)
- New document: Automatically determine next sequence number, given the rest of the document code (item 2.9, difficult)
New document: Set classification fields button, works like Preview but stays in input form (item 2.13)
- New document: Custom input template that highlights classification fields that are part of the drawing code
- 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.
- 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?
- 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.
- New comment: Add ability to add/remove subscribers when the comment is created
- Generate an email when a revision is rejected (how? to whom?)
- Implement additional document search fields:
- Dates for planned workflow steps
- Initials for workflow steps
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
- Software updates that require a data model change:
- 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
- Implement record versioning, to allow a field level audit trail
- 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
- Implement new public/private field: 3-date flag to make public to contract or system (item 3.13)
- Reference data and drawing code configuration:
- New task types:
Ablehnung - To document why a revision was rejected
- New revision types:
Vorabzug
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:
- Kontakt
- Objekt
- Dokumenttyp
- 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
- 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, ...
- New task types:
- Site settings:
- Documents: Set all classification fields that are mapped from the drawing code required
- Complete translation of reference data:
- Comment types
- Translation
Main menu: Rename Submittal (in DE) as Versand
- What names to use in EN version?
- Input fields names in task search
- Classification attributes:
- Fachgebiet is dependent on Fachgebiet. Solve with V12.x. (item 3.3)
- Deployment: Goal is DrawMGT deployment by end Nov (excluding Wiki)
- Prepare configuration on lu.softxs.ch for ssh tunnel
- Test ssh tunnel
- Negotiate procedure with Axpo Unix specialist (Jörg Leppin) for getting access
- Alway available
- On demand via email/telephone
- crontab
- Ensure all required tools available
- MySQL
- PHP - including MySQL access
- Apache - including support for PHP5
- htmldoc
- Perl and PHP extensions
- Outgoing email configuration
- Apache configuration
- php.ini configuration
- For Apache
- For PHP called from command line (may be a different php.ini file!)
- Test DrawMGT installation
- Prepare configuration on lu.softxs.ch for ssh tunnel