Use Cases - UC-04 Artifacts

• User must be logged
• User must have ROLE_PRODUCT_MANAGER

1. User request to upload artifacts by version identifier
2. System returns modal component to upload multiple large files.
3. User adds artifacts and start upload process.
4. System starts upload in background and notifies the user after completion.
5. System saves artifact to the underlying datastorage
6. System calculates MD5 over the uploaded artifact
7. System creates an artifact metadata entry with storage stats.
8. Version UploadDate must be updated.

• User must be logged
  • User could have ANY ROLE

1. User request to obtain an artifact from the repository by identifier
2. If user has ROLE_CUSTOMER licenses must be validated (@see UC-03g VersionManagement - validateLicenses)
3. Once validated, system recovers artifact from underlying storage and returns to the user as a downloadable item.
4. System audits the artifact downloaded by the customer for stats pourposes.
5. System may show a progress bar of the download process.

System will raise and exception if primarey key does not exist.

System will raise and exception if license could not be validated

• User must be logged
  • User could have ANY ROLE

1. User request to obtain the whole bunch of artifacts of a version.
2. System recovers all the artifacts (@see UC-04c ArtifactManagement-GetArtifact). 
3. System packages all the artifacts in a single zip package.
4. System audits the artifact downloaded by the customer for stats pourposes.
5. System may show a progress bar of the download process.

System will raise and exception if primary key does not exist.

System will raise and exception if license could not be validated

• User must be logged
• User could have ANY ROLE

1. User request the details of a version
2. System retrieve artifacts metadata of current version and show it to the user

None

• User must be logged
• User could have ROLE_PRODUCT_MANAGER

1. User request to remove an artifact.
2. System will warn about the loose of data (storage and metadata).
3. User accepts to remove the version.
4. System removes version from storage and deletes the associated metadata.

None