Skip to end of metadata
Go to start of metadata
This page describes the steps to releasing screen definitions for OOINet

Development Process

Editing the UI Database

  1. Get on the OOI secure network (from UCSD or using VPN)
  2. Use Remote Desktop Connection (RDC) to connect to filemaker.oceanobservatories.org
    • Mount a local drive as network drive for RDC as TRANSFER (so that within filemaker Windows VM you have a path to a local directory)
  3. Close any open FileMaker Pro window on the VM
  4. Copy "ciux specifications.fp7" to TRANSFER/filemakerdb/ciux specifications.fp7
    • The Release 3 master file is in directory "C:\Filemaker Data"
    • The Release 2 branch head file is in directory "C:\Filemaker Data\Release 2"
    • This downloads the database to the local machine
  5. Make a local DB copy of the transferred original and name it "ciux specifications_20140317.fp7" – use current date
  6. Edit "ciux specifications.fp7" on local machine
    • Enter log statement describing changes
    • Try out your edits by exporting them to CSV locally
  7. On filemaker VM rename current database to "ciux specifications_20140317.fp7" – use current date
  8. Using RDC copy from TRANSFER/filemakerdb/ciux specifications.fp7 to Filemaker Data directory
    • Make sure you copy to the right Release 3 or Release 2 directory – don't mix them up

Database Export Deployment

Release 3 Export

  1. On filemaker VM, open network drive to userexperience server ( Z: )
  2. Make a copy of userexperience/R3Stable as userexperience/R3Stable_20140317 – use current date
  3. Rename userexperience/R3Candidates to userexperience/R3Stable
  4. In Filemaker, execute Scripts/Export/Export R3 macro to export to userexperience/R3Candidates
  5. Make sure not export errors occurred and check that all expected files are present in the export directory
    • In case of error, revert the chances to R3Stable and R3Candidates

Release 2 Export

  1. On filemaker VM, open network drive to userexperience server ( Z: )
  2. Make a copy of userexperience/Stable as userexperience/Stable_20140317 – use current date
  3. Rename userexperience/Candidates to userexperience/Stable
  4. In Filemaker, execute Scripts/Export/Export macro to export to userexperience/Candidates
  5. Make sure not export errors occurred and check that all expected files are present in the export directory
    • In case of error, revert the chances to Stable and Candidates

Proposed Improved Process

  • CVS file exports are committed to ion-ux repository as /ui_specs directory
    • A new ion-ux commit updates CSV exportsand any Python and JS code that is necessary matching the updated screen defs
    • Indicate which coi-services commit or release the ion-ux commit is consistent with
  • The ion-ux code, e.g. in main.py generates the ui_specs.json file from the CSV files and stores it locally if not existing or on demand
    • e.g. python parse_specs.py ui_specs/r3candidate
  • Alternatively: Commit ui_specs.json to the repository and config point to it
  • Change ion-ux code to load ui_specs.json file instead of making a backend service call
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.