minond / captainslog Goto Github PK

• Search endpoint
• Search UI

• List items in book page
• Views for showing/editing resources
• Controllers for creating/editing resources
• Handle update operation
• Handle create operation
• Reprocess entries

Either style it correctly or have it go back to the homepage. In either case make sure to add an error message.

Could use JWT's for authenticating web client. Just need a user's guid in the session.

• Update user model to store auth related info
• Create user with auth info
• Be able to authenticate a user in service
• Login endpoint
• Login form
• Generate JWT
• Inject token into HTML response
• Pass JWT from client in every request
• Read JWT into session
• Generate token endpoint
• Update seeder with authentication
• Handle page refreshes
• Logout

Connections allow users to pull data from various sources into their books.

• Connection CRUD operations
• Setup oauth connection
• Store credentials
• Update refresh token changes
• Bind connection to book
• Job model and infrastructure
• Data sync command/logic
• Prevent data duplication
• Initiate data sync on connection update
• Initiate data sync on schedule

Instead of storing in memory.

Create data slurping API/UI and connect to Food Data Central API.

You are receiving this email because you are a user of the USDA Food Composition Database API at https://api.nal.usda.gov/ndb. We wish to inform you that the API is scheduled for end-of-life (EOL) on March 31, 2020. No further updates to the database nor modifications to the API will be made during the transition period.

The API is being replaced by the Food Data Central API. Documentation for this API is available at https://fdc.nal.usda.gov/api-guide.html. Additional information on Food Data Central is also available at https://fdc.nal.usda.gov/faq.html. We urge you to transition your use of the Food Composition Database API as soon as possible to the Food Data Central API.

Please use the api.data.gov issues tracker at https://github.com/USDA/USDA-APIs/issues to submit your questions, comments or concerns regarding this transition. We especially welcome suggestions for enhancements to the Food Data Central API. We anticipate a new version of the Food Data Central API incorporating feedback received from users will be available by January 15, 2020.

CL is currently using the default Rails pages. These pages should be updated to match CL's theme and provide useful actions for users to take when they reach one of these pages.

• Render reports
• Link outputs to inputs
• Load data
• Missing inputs report output
• Loading report output
• Models
• Create report
• Update report
• Delete report
• Create output
• Edit output
• Delete output
• Create variable
• Edit variable
• Delete variable
• List reports

Like in the Puller app. It may be good to extract the logic current in the cable connection/channel and place it in the component get or equivalent.