Enterprise data import feature
Use Case
User Scenarios
If a platform wants to import their data on a portal as a first step, they will want an easy way to create their enterprise data.
Currently if the urlid of an enterprise that doesn't exist in the database is included in a CSV file, it will be created in the database with only the urlid populated.
Business Motivation
Give a simpler option to start interacting with the standard than the whole OIDC authentification process.
Expected Outcome
Benefits for the User
Interact quickly with the DFC community
Success Criteria
Give options to platform like Arrivage to join the CQCM map with their enterprise and product data.
Specifications
Current State
Currently the enterprise data (on the proxy side) is imported from the data-server (a priori) but the djangoldp-csv package is generic, meaning that we could also upload enterprise data via CSV if needed
Expected Behavior
When subscribing to the portal, I have the option to upload a csv. This csv can create one or several enterprises or products or both.
When creating an enterprise, we need to make sure there is a way to receive
Functional Requirements
- List technical or functional elements that must be implemented.
- Include conditions, validations, edge cases, etc.
Acceptance Criteria
This section needs to be improved
- Import the template file
- Observe the data were created in the admin