For some reason, our dev DB is growing. I suspect there are conflicts that are getting synced, possibly from the populateOffline for Tally app which creates 600+ species records.

Set up Couch for OTS

https://nwcdevfram2.nwfsc2.noaa.gov:6984/_utils/

Currently doing this for obs-electron.

It makes sense to do this after doing the npm outdated and npm update commands in ticket #7

To fix the security warnings that node spits out after an npm install, run npm audit and execute the suggested update commands to fix any critical or high (optionally Medium or Low if you want) warnings. . I'd avoid updating Low priority issues with a SEMVER WARNING: Breaking Changes warning.

There's an npm audit fix command which is supposed to do this automatically, but it's not working for me, so I did it manually.

-- Select Permit, which then tells us the fishery

--- Non-Permitted Fisheries include:
---- Open Access
--- Permit Not Available (i.e. we haven't uploaded it yet)
---- Allow skipper to be able to type it in, want Observer staff confirmation
---- Or skipper potential enter their L number (CDFW license number)

-- Add Start Time
--- LOGIC - If trying to start within 48 hours, notice that they may be held up,
this is only for EM EFP. For non-EM EFP, will be reduced to 24 hours

-- Add End Time
-- Add Departure Port (default to the Home port in User Preferences)
-- Add Return Port (default to same as Departure Port)

-- Add Home Port field
-- Add Address fields
-- Add Banner / Alert options as well

Specify how we will be creating and bundling applications for our different configurations using json configuration files. The initial configurations will include:

• Observer-Electron
  -- WCGOP
  -- A-SHOP

• Survey-Cutter
  -- Trawl Survey
  -- Hake Survey

I would note, for the Observer-Electron, we might actually want those different configurations to be specified on the fly within the application after the user selects the fishery, i.e. if A-SHOP is selected, use the A-SHOP configuration, else use the WCGOP configuration.

npm install (from Visual Studio command prompt) yields an error that I hadn't seen until today:

LINK : fatal error LNK1181: cannot open input file 'C:\OpenSSL-Win64\lib\libeay32.lib' [C:\git\boatnet-local\observer\o
bs-electron\node_modules\rsa-keygen\build\rsa_keygen.vcxproj]

Fix will probably be to install http://slproweb.com/download/Win64OpenSSL-1_1_0i.exe (note the "i") to the C:\OpenSSL-Win64\ directory.

We'll need to update README/ CONTRIBUTING once I verify this is the only requirement to fix it.

Add Vessel Reg number, only staff can edit vessel info, merge Coast Guard # and State Reg # into one field

Implement footer functionality per page.
Also consider - should the footer be a solid bar, or would floating rounded buttons be nicer?

When user Add Trip or Edit Trip from Trips page, load that trip into Trip Details and persist edits to PouchDB.

This task is to move the shared data models from obs-electron into a fram-modules 'fram-models' module.

Leverage ideas from A-SHOP NORPAC Data Editor (NDE) and WCGOP OBSPROD Debriefing component, as well as McVeigh's excel proposed mockup.

Create mockups using Balsamiq for the following platform screen sizes, orientations, and projects:

Platform + Orientations

• Tablet landscape
• Tablet portrait
• Desktop landscape

Projects

• Observer-electron
• Survey-cutter

Looks like img/visualStudioScreenshot.PNG needs to be added to the repo, noticed a broken image link on obs-electron/README.md

And one new addition:

• To build correctly on Windows, the crypto-pouch library requires OpenSSL v1.0.2 and optionally v1.1.0 to be installed to C:\OpenSSL-Win64\ (which is not the default install directory.)
  Required:
  http://slproweb.com/download/Win64OpenSSL-1_0_2p.exe
  Optional, but recommended as well:
  http://slproweb.com/download/Win64OpenSSL-1_1_0i.exe (note the "i" version.)

If installed correctly, the build will be able to locate the file C:\OpenSSL-Win64\lib\libeay32.lib

-- Investigate to determine if possible

per the mockup: https://drive.google.com/file/d/1jkRivBnHuYMPNXbquwX9E-rNFLMmQPZ2/view?usp=sharing
build the user preferences page

We'll want to document git commands for our team workflow:

1. creating feature branch
2. keeping branch up-to-date with master via rebase or merge
3. creating a pull request
4. merging back into master

Communicate with auth server (private repo) but with a flag for local debug development.

In terms of actually populating these lookup documents, we could populate them in one of two ways:

• Bulk populate up front with all of the OBSPROD lookups and other lookups data
• Populate individual lookup documents as the need arises for given boatnet software components

We also need to determine if we will keep these lookup documents in the same couchdb instance as the user collected data or in a separate lookups couchdb instance.

-- Initiation via Captain, Observer, or Observer Staff
-- If via Captain, then Observer or Observer Staff must approve
-- If Observer or Observer Staff, then Captain concurs

just making a test issue.

Determined each trip should be it's own doc - if possible, it will be the same trip an observer uses on tablet

Getting away from Fram-, using bn (boatnet) instead

Per mockup: https://drive.google.com/file/d/1jkRivBnHuYMPNXbquwX9E-rNFLMmQPZ2/view?usp=sharing
build the manage permits page

Throwing this your way @wsmith-nwfsc as @melinashak-noaa is focused on EDC deployment this week (and likely next as well)

fix

There is a useful command to check if your packages need upgrade (security updates, etc) which is:

npm outdated

This will show "Current", "Wanted" (which is newest compatible version), and "Latest" which can be incompatible with what you're running. Packages listed in red should be updated, and yellow is recommended. To automatically update your package.json to "Wanted" the command is:

npm update
This also seems to implicitly run npm install Then re-run to make sure everything's up to date:
npm outdated

Created this ticket to track this operation for obs-electron to try and reduce the security issue warnings. @sethgerou-noaa we should do this step regularly for obs-web as well.

Source for this I came across: https://docs.npmjs.com/getting-started/updating-local-packages

If user has selected "Email" in OTS User Config, they should receive an email any time the trip is modified - to include:
-Staff editing the trip
-A selection decision change
-A message being added to the trip
-A specific observer being assigned to the trip
-The trip status is changed

Currently getting this error on a clean install, when running ng serve:

ERROR in node_modules/@angular/flex-layout/core/typings/observable-media/observable-media.d.ts(11,14): error TS2416: Property 'subscribe' in type 'ObservableMedia' is not assignable to thesame property in base type 'Subscribable<MediaChange>'.  Type '(next?: (value: MediaChange) => void, error?: (error: any) => void, complete?: () => void) => Sub...' is not assignable to type '{ (observer?: PartialObserver<MediaChange>): Unsubscribable; (next?: (value: MediaChange) => void...'.    Types of parameters 'next' and 'observer' are incompatible.
      Type 'PartialObserver<MediaChange>' is not assignable to type '(value: MediaChange) => void'.
        Type 'NextObserver<MediaChange>' is not assignable to type '(value: MediaChange) => void'.
          Type 'NextObserver<MediaChange>' provides no match for the signature '(value: MediaChange): void'.

May be related to b269ce9
Fiddling with ng upgrade and will see if I can remedy.

Fix wikis for capturing requirements for observer and survey screens and functionality