iscc / iscc-web Goto Github PK

View Code? Open in Web Editor NEW

5.0 1.0 2.0 741 KB

Minimal ISCC Generator Web Application

Home Page: https://iscc.io

License: Apache License 2.0

Python 65.88% HTML 7.87% JavaScript 0.92% Vue 19.70% TypeScript 3.13% Dockerfile 2.36% SCSS 0.16%

content-identification iscc web-application

iscc-web's People

Contributors

Stargazers

Watchers

Forkers

relves jmiziolek

iscc-web's Issues

Skip recalculation of Content-Code after metadata embedding.

Add background task for cleanup of expired uploads.

Document configuration options

Restrict file downloads to original uploaders.

Document how file upload works (including curl examples)

Docker (compose) setup for dev and deployment.

Handle unsupported media types in backend

with early interruption of upload and helpful status code response.

Add link to source repository in footer.

Create endpoint for ISCC decoding and frontend visualization.

Add endpoint that generates ISCCs from URLs

An endpoint that accepts a media asset URL and embeddable metadata as input.
The service should download the asset, embed metadata (if any), generate an ISCC asynchronously while blocking the client until the response is ready. The URL of the modified local media asset will be in the response so it is available for download within the cleanup timeout.

Open Questions:

Should the download be locked to the IP that created the request or should it be open for download.

If the processing result and/or modified asset needs to be stored somewhere else it might make sense to allow to provide a callback URL with the request, such that the server can push the result(s) to the provided callback URL.

If there is a callback URL the server wouldn´t need to block the client. Instead the server could return a job-id instantly. If the client needs to know the job status it could query the server.

Add CI testing

Add link to API docs to demo frontend.

Process new ISCC automatically when embedding metadata.

Add version information to footer.

Support deletion of uploaded files from frontend.

Uploaded files are deleted automatically after 60 minutes and can also be deleted manually via API. Add support for user triggered deletion via frontend. We could delete files when the user closes the result panel or add a dedicated button for deletion.