svkurowski/aktenkoffer

💼 Personal document management made easy.

aktenkoffer's Issues

Async upload on documents index page

Allow to upload document straight from index page using AJAX (just the file, no other fields). If one document is uploaded, redirect to that documents show page. If multiple documents are uploaded, show a list of them with links to their show pages.

Enable users to input `null` for `received_at` and `sent_at` fields

Also, possibly we can use native HTML date input or a JS date input

Add linter

• MUST include CircleCI config to execute the linter on every PR
• SHOULD include information on running the linter from CLI in README.md
• MAY include information on setting up a pre-commit hook that runs the linter in README.md

Tags input has some visual issues (Firefox / Windows)

Page overflows viewport resulting in scrolling

Somehow the body of the page is larger than the viewport and thus it's possible to scroll the page even though the content is completely inside the viewport. I believe this is caused by the padding on the .section. Need to reproduce with basic bulma page (e.g. JSFiddle).

Make original file on Document model required and readonly

Add button to swap document sender and recipient

User authentication with cookies

We should authenticate the user using cookies and not basic authentication. We can consider allowing multiple users in one instance although I'm not a fan of that so far because it increases complexity.

Using async job, extract text from PDF and store it in DB

For now, this should actually just use the embedded text and not do any OCR on it's own - that is still the client's responsibility.

The text should not be exposed in documents#show or documents#edit.

The use case is to be able to later search documents by their contents as well as automated title and date extraction.

The PR must include setting up the job handler in Heroku.

When dropping a file, the file name label is not updated (Firefox / Windows)

Still shows "No file chosen", but the file is actually there (when submitting it is uploaded correctly).

Add AWS Cloudformation template for S3 Bucket and IAM user

Add AWS Cloudformation template for S3 Bucket and IAM user to make creating a new instance easier

Move document edit and delete links from index page to show page

At the moment, we expect users to:

1. Create documents a lot
2. Search/index documents a lot
3. Edit documents rarely
4. Delete documents almost never

Thus, we do not need the edit and delete document links as easily accessible on the index page. Advantages of moving them:

• Can make whole document row clickable on index view instead of having show button
• Thus, more possibilities for a nicer design of a single document on the index view.

(This will change in the future, especially 3. for which we want to enable users to create raw/no-info documents and add that later but we can revise this then).

Cover analyze_document job in tests

Cover analyze_document job in tests

Would have prevented 900695c

500 error when uploading multiple documents from index view

LoadError
Unable to autoload constant Api::DocumentsController, expected /Users/svkurowski/Projects/aktenkoffer/app/controllers/api/documents_controller.rb to define it

Add app.json for Heroku

Official documentation here

We at least need to specify the build packs key to say that heroku/nodejs and heroku/ruby are required. Also, this would be very helpful initial documentation of all the environment variables.

Make document edit view consistent with document show view

It could look basically the same. The form elements should be in the right column. We could consider reordering the columns on mobile so that the form comes above the preview but not sure whether that is a good idea.

Create home contact in seeds

We can create a home contact with hardcoded id and name in seeds, and use this by default. That way, new users won't have to restart the app after creating their own home contact.

Tagging of documents

Enable user to set and view tags on documents

Add linter for JavaScript code

And possibly for SCSS as well?

As with rubocop, should be integrated with CircleCI

Remove all respond_to blocks

As discussed with @markokajzer we will create separate controller classes in an API namespace so we can safely remove the respond_to blocks and support for JSON format from the regular controllers.

Move contacts creation functionality to document#new and document#edit

We shouldn't need separate contacts views.

Definition of done:

• Contacts input on document form is a searchable select / text box
• Users can create a new contact right from the document form (e.g. using Modal or just by inputting contact name)

Why is this a good idea? Right now, when I upload a new document for which I don't have a contact created yet, I need to move to contacts page, create the contact, go back to document#new page, input everything again and select the new contact.

Pagination of documents

Workaround for Safari Bug: Redirect in Object Tag data attribute breaks the preview

Safari Version 13.1.2 (14609.3.5.1.5)

Instead of PDF preview, it just shows a gray box.

Stackoverflow reference: https://stackoverflow.com/questions/41070632/how-can-i-get-a-pdf-to-display-in-an-object-tag-in-safari-when-the-data-is-a-3

As a workaround, we can use service_url for Safari which avoids the redirect

Error when running rake assets:precompile

Running via Spring preloader in process 24549
Yarn executable was not detected in the system.
Download Yarn at https://yarnpkg.com/en/docs/install
rake aborted!
LoadError: cannot load such file -- coffee_script
-e:1:in `<main>'
Tasks: TOP => assets:precompile
(See full trace by running task with --trace)

Note: The error about Yarn is okay and was there before, but the load error about coffee script is new and is making rake exit with error.

Known-good commit: 293ae1b

Implement API key authentication for API access

User should be able to create API keys. All APIs should be able to be called using these API keys. This is useful for e.g. scripts that perform scans of a document and then immediately upload the file to Aktenkoffer.

If sender/recipient is selected, set the other to home contact if still empty

Idea: Add support for Cloudinary to get 1-click "Deploy to heroku" functionality

Filtering of documents based on simple query language

Initial version: filter just on title and maybe sender/recipient
Next step: Filter on other fields using search operators such as in https://support.google.com/mail/answer/7190?hl=en

Don't use elastic search or something like that, just PostgreSQL's text search feature