Valdin Cloud
Budget: $1,500 – $3,000 USD
Valdin Cloud Requirements
Content Access - Using World Wide Web-supported application guidelines, an app will be designed and produced that can be released and accessed by those with a browser on the web, under a restricted access site..
App Scope - The app will be towards geared towards the uploading, annotating, categorizing and serving of digital assets.
App Access - End users will access the backend for the WWW app via API.
Media Management Accommodating - WWW App - Static text, image, video files, audio, PDFs, and similar documents - this system will allow a Web end user to upload and search an existing archive that is arranged by multiple categories, tags and configurations, each of which can be saved and made accessible via API, or some other query mechanism.
API Development & Standards of Access - In addition to the management system, an API with secure key will be made available to the end user seeking to pull media from the platform into their own projects.
Asset Storage Design Project - media will be uploaded and tagged using tools such as cloud storage and dbase. Facial recognition and transcription tools will be integrated as feasible e.g. machine learning, AI, etc.
Multitenancy - Users will be able to create their own archives and access separate endpoints that do not conflict with other users on the platform.
Data Encryption Where feasible - user data will be encrypted at rest, and transmitted using https to help maintain user privacy.
Alternative Authentication/Two-Factor - Users can create accounts using passwordless authentication (email verification like the service Medium uses) and/or opt for two-factor authentication. No passwords are stored with the platform, limiting the impact of any data breach, whether on platform or with an external service the user may be using the same password to access.
Subscription Based - the client will have the ability to renew or cancel services e.g. each month, or year.
Documentation - All system architecture and code, where possible - this platform will need to be thoroughly documented to support future development work and maintenance.
Project Management - Recurring updates to help with communication on key development stages.
Ownership - Project owner will own the code, architecture, content solution, etc. at the end of the project.
Content Access - Using World Wide Web-supported application guidelines, an app will be designed and produced that can be released and accessed by those with a browser on the web, under a restricted access site..
App Scope - The app will be towards geared towards the uploading, annotating, categorizing and serving of digital assets.
App Access - End users will access the backend for the WWW app via API.
Media Management Accommodating - WWW App - Static text, image, video files, audio, PDFs, and similar documents - this system will allow a Web end user to upload and search an existing archive that is arranged by multiple categories, tags and configurations, each of which can be saved and made accessible via API, or some other query mechanism.
API Development & Standards of Access - In addition to the management system, an API with secure key will be made available to the end user seeking to pull media from the platform into their own projects.
Asset Storage Design Project - media will be uploaded and tagged using tools such as cloud storage and dbase. Facial recognition and transcription tools will be integrated as feasible e.g. machine learning, AI, etc.
Multitenancy - Users will be able to create their own archives and access separate endpoints that do not conflict with other users on the platform.
Data Encryption Where feasible - user data will be encrypted at rest, and transmitted using https to help maintain user privacy.
Alternative Authentication/Two-Factor - Users can create accounts using passwordless authentication (email verification like the service Medium uses) and/or opt for two-factor authentication. No passwords are stored with the platform, limiting the impact of any data breach, whether on platform or with an external service the user may be using the same password to access.
Subscription Based - the client will have the ability to renew or cancel services e.g. each month, or year.
Documentation - All system architecture and code, where possible - this platform will need to be thoroughly documented to support future development work and maintenance.
Project Management - Recurring updates to help with communication on key development stages.
Ownership - Project owner will own the code, architecture, content solution, etc. at the end of the project.