V2 - Uma Oya
Goals
Discussion notes AH & JK 2014.09.04
- Step-wise import of the Uma Oya transmittals, drawings, etc.
Start with the JV to Farab letters in the Excel Outgoing Register
- Create the letter metadata
- Upload the transmitted documents as attachments to the letters
- Accept that there will be duplicates of files in the as the additional metadata is created
- Create initial spreadsheets of transmittal and document lists that:
- Can be completed and corrected by hand by project personnel
- That can be used to generate:
- Metadata upload files
- Scrips for renaming transmittal direcrories, document files, etc.
Overview
- Upload metadata for letters
- Upload the transmittal attachments as attachments to the letters
- Create Transmittals in System for Drawing Transmittal Letters
- Find and Upload the Source and Publish Files
Parties involved:
- MG (Mahad Ghots) - Lead partner in Joint Venture
- Pöyry - Doing project management for the client
- FAB (Farab) - The EPC contractor and designer/builder
- JV - The Joint Venture doing the project
There are two letter registers:
Incoming - Letters received by Pöyry from MG, and letters received by the JV from Farab
Outgoing - Letters sent by Pöyry to MG, and letters sent by the JV to Farab
There are four streams of letters:
- Pöyry to MG
- MG to Pöyry
- JV to FAB
- FAB to JV
Letters are either:
- Transmittals with associated drawings, reports, etc.
- Normal letters
Initially start working on the JV to FAB letters.
See the Uma Oya Quickstart guide in the tracking system for notes on how letters should be coded and filed.
Create Metadata for Letters
Check and potentially update the coding scheme for the letters. Suggest:
- Sender code
- Recipient code
- Date
Check and potentially update the object types and classification schemes:
Use the Letter object type for letters.
Use the Issued revision type for letters
It uses the Issued revision classification scheme
We might add a Is transmittal classification field to the corresponding document classification scheme and possibly other fields, depending on what information is available in the document registers.
Need to add workflow classification fields to the revision classification scheme (or create a new one) for letters.
Upload the transmittal attachments as attachments to the letters
- Look in the Uma Oya document directories:
- Analyze the file types in the directories and identify non-document file types (Thumbnails, etc.)
- Delete all them
- Upload the letter file as a revision file (in an automated way)
- Create a note to attach the documents to
- The lette
- (WIth text simething like "attached files")
- This is a temporary solution
Create Transmittals in System for Drawing Transmittal Letters
- Ignore all the non-transmittal letters and focus on the letters that are really transmittals
- Create the document metadata (but no files)
- Need to create the correct document codes
- And associated classification information
- Create maximum amount of information that can automatically be determined from:
- The files in the Uma Oya document directories
- The letter registers
- Put the information in a spreadsheet and have project people check and fill in missing information
- Need to create the correct document codes
- Create a transmittal in the system
By cloning the trasnmittal letters into transmittals
- Create the document metadata
- For each transmittal create spreadsheet data with the correct drawing code and classification data
- This gives us a list of all drawing numbers
- Attach the document to the transmittals
Issue: This may not be possible to attach the documents, given there are no document files yet
- Create dossiers for each transmittal instead, or use links?
Find and Upload the Source and Publish Files
- For each transmitted document find the source and publish files
- Make sure the files are named correctly
- Could by done be creating a spreadsheet of the files in transmittal dircetory
With columns current file name and expected file name
- Use the spreadsheet to generate a script to rename all the files