formkiq-core
formkiq-core copied to clipboard
formkiq
A full-featured Document Layer for your application, providing the functionality of a flexible document management system, including storage, discovery, processing, and retrieval. Deploys directly int...
It would be great if Documents could have permissions based on the https://www.openpolicyagent.org/ Document "locking" could also be implemented using this.
AWS has added a Lambda extension for retrieving SSM parameters / secets that could be used instead of the SsmService currently being used. https://aws.amazon.com/about-aws/whats-new/2022/10/aws-parameters-secrets-lambda-extension
There's a number of full text search engines that could be support in addition to [OpenSearhc](https://opensearch.org/) - https://github.com/valeriansaliou/sonic - https://jakejscott.com/full-text-search-for-dynamodb-using-lambda-efs-tantivy-and-rust
java.io.IOException: unable to update Fulltext at com.formkiq.stacks.api.handler.DocumentTagsRequestHandler.updateFulltextIfInstalled(DocumentTagsRequestHandler.java:286) at com.formkiq.stacks.api.handler.DocumentTagsRequestHandler.post(DocumentTagsRequestHandler.java:218) at com.formkiq.aws.services.lambda.AbstractRestApiRequestHandler.callHandlerMethod(AbstractRestApiRequestHandler.java:166) at com.formkiq.aws.services.lambda.AbstractRestApiRequestHandler.processRequest(AbstractRestApiRequestHandler.java:411) at com.formkiq.aws.services.lambda.AbstractRestApiRequestHandler.processApiGatewayRequest(AbstractRestApiRequestHandler.java:349) at com.formkiq.aws.services.lambda.AbstractRestApiRequestHandler.handleRequest(AbstractRestApiRequestHandler.java:286)
POST /documents/{documentId}/action - adds document action but the action is never processed.
If a document fails to process, it should be moved to a dead-letter S3 bucket to allow for reprocessing or tracking which documents failed to load.
* Add Running Status * Add Start / Stop Timestamps for each Step * Add Number of action Retries before failure
For deep links, using the deepest-level name may work in some cases, such as SharePoint (?), but for Google Drive, that name is an ID, rather than a human-readable name....
Currently, GET /documents returns only from the current day, which is not as intuitive as a full GET of documents. Ideally, this request will not restrict itself to the current...
When querying meta data in POST /search, the documentids is ignored { "query": { "meta": { "indexType": "folder", "eq": "Contacts/51bbe19d-14cc-42cf-a872-2b2e6d322ed3" }, "documentIds": [ "9e2aa589-d1b8-4b99-b8d8-1c4c641a80bd" ] } }