osu-cascades / batabase Goto Github PK

manually create inside create db

Contacts differ from users in that they do not have a log in, for now lets have two tables Users & Contacts

confirm owning agency relationship

Build out:

• Sign up
• Sign in
• Profile, edit profile

Choices: ODFW, NPS, BLM, USFS, OSU, Other

Is this going to be one or two screens? What exactly is the workflow?

locationDescription is a text type which includes many attributes that need to be broken up into their own columns.

alter path for user edit,
provide more granularity for editing users

• Talk w/ Roger and Tom about welcome screen content. Should there be a welcome screen at all? If not what screen are you directed to after sign in/up?

GRTS
State
County
State2
County2
SpeciesGroup FK

I see value in the ability for a user of the web-app to be able to look at their current profile information and permissions as opposed to just dropping them inside an edit form.

This would also make it easier to manage what a user can and can't edit (permissions, agency etc)

• Confirm workflow of viewing all species groups and how to add another one
• Add species group to list maintenance

Due to governmental privacy concerns, users should only be able to gain access to Batabase via an invitation from an administrator.

• Remove public signup page
• Create workflow for admin to invite new user via email
• Email should link invitee to private sign up workflow

• Remove from prototype
• Drop table, update schema

• Remove from prototype
• Drop table, update schema

Use devise gem
Additional fields: email, first/last name, organization, state

Roles
Administrator
Field Agent
Guest

• Remove from static prototype
• Drop table, update schema
• Remove model/specs

• add to list maintenance
• add target descriptor table

AcceptableCallQuality: Double, Default: 0.80
SqncDecisionThreshold: Double, Default: 0.90
MaxNoCalls: Integer, Default: 16
LogfileNotes: Long Text

• Remove from detector list headings
• Remove from edit/new forms

In list maintenance what is distance ranges used for. Do we need it in list maintenance?
Can it just be a numerical input? What table would it belong to?

Every page but login.
before_action :authenticate_user!

prototype/sample-unit/sample-unit.html is currently a form. Need to update to show a list of all Sample Units with option to add/edit/delete.

• Add to list maintenance
• Add drop down selection to users
• Add drop down selection to contacts

QuadID: Can only be: NE, NW, SE, SW
QuadNo: Can be: 1 to 20
LocationID: equals SampleUnit + QuadID + QuadNo (123456_NE1), autofills from entries
DrivingDirections: Long Text
DetectionTargetID FK: references a new table, see tluDetectionTarget
TargetDescriptorID FK: references a new table, see tblTargetDescriptor

Flesh out admin dashboard in HTML. Are there additional screens we need?
Invite user screen?
Edit user screen?

• Add text area to prototype DeploymentLocations form
• Remove drop column from script
• Rename column to fit rails standards
• Model validations?

• Contact dropdown (contacts will need to be added to list maintenance)
• Detector dropdown

• Remove profile image (there is no image upload option in sign up or edit forms)
• While waiting for feedback lets add all user fields from DB frontend

• Confirm w/ Roger and Tom which user fields they want

• Rename contacts table to users in update-db.sql script.
• Update table to support devise https://github.com/plataformatec/devise/wiki/How-To:-Change-an-already-existing-table-to-add-devise-required-columns
• Add devise gem
• rails generate devise User

The deployment form is missing the 'Detection Inputs' section (Sonobat/Kaleidoscope).

Consider the situation of sending the client a link to tinker w/ the experience:

http://batabase-staging.herokuapp.com/

The sign in screen is displayed. Is that what the public sees when they visit the app?

Revisit the initial UX in the prototype and ensure that clicking the "sign in" button results in something.