Vinyl collection management system

1. A short description. Note that the client is not having a technical background.

   Vinyl Collection Management App tailored to meet the needs of vinyl enthusiasts and collectors. Users can add vinyl records to their collection by inputting information such as album title, artist, release year, genre and the date aquired, the app will also support image uploads for cover art. Users can easily add, edit and delete records from their collection. The app will support offline access, enabling users to manage their collections even without an internet connection.

2. Domain details. Present the details of the entities that will be persisted. Each field should have a description.

   Entity: Record

   Attributes:

   1. title: description of the vinyl record's title or name
   2. artist: name of the artist or band that created the record
   3. release year: the year when the vinyl record was released
   4. genre: the music genre or category to which the record belongs
   5. date acquired: the date when the user added the record to their collection
   6. cover: an image of the record's cover for visual reference

3. CRUD. Present the details of each crud operation. - create. - read. - update. - delete.

   create:

   • the "create" operation allows users to add a new vinyl record to their collection
   • implementation:
     • users will press a + icon button promoting them to a "Add New Record" form
     • they will input the following information:
       1. title: mandatory
       2. artist: mandatory
       3. release year: optional
       4. genre: optional
       5. date acquired: optional
       6. cover: optional, but has a default image
     • after entering the details, users will click a "Save" button
     • the system will validate the input and store the new vinyl record in the database and the record will appear on the home page

   read:

   • the "read" operation allows users to view information about vinyl records in their collection
   • implementation:
     • users will have access to a list view of their vinyl records
     • when they select a record, they can view, on a different page, its details, including all fields like title, artist, release year etc.

   update:

   • the "update" operation enables users to modify the information of an existing vinyl record
   • implementation:
     • users will select a vinyl record they wish to edit from their collection
     • the system will present an "Edit Record" form pre-populated with the existing record's information
     • users can modify any field, including the title, artist, year, genre, etc.
     • after making changes, users will click a "Save Changes" button
     • the system will validate and update the record in the database and the updated record will appear on the home page

   delete:

   • the "delete" operation allows users to remove a vinyl record from their collection
   • implementation:
     • users will select a vinyl record they wish to delete from their collection
     • the record will be permanently removed from the database, and the user's collection will be updated accordingly
     • deleted records should not be recoverable to prevent accidental data loss

4. Persistence details, what crud operations are persisted on the local db and on the server.

   create:

   • when a user adds a new vinyl record, it is first stored in the local database for quick access and offline functionality
   • a copy of the new record is saved on the server to provide data backup

   read:

   • viewing and retrieving vinyl record information primarily relies on the local database, ensuring access even when offline
   • the server maintains a copy of the user's vinyl collection

   update:

   • editing an existing vinyl record instantly updates the local database, reflecting changes for the user
   • the update operation synchronizes with the server to maintain data consistency

   delete:

   • deleting an existing vinyl record instantly updates the local database, reflecting changes for the user
   • the update operation synchronizes with the server to maintain data consistency

5. Details on what is happening when the device is offline.

   when offline:

   • the app will primarily rely on the local database for all CRUD operations (Create, Read, Update, Delete)
   • the app should provide clear and user-friendly feedback to inform users when they are offline

   create:

   • users can still add new vinyl records to their collection when offline
   • the app will store these new records locally on the device immediately
   • the records will be marked as "pending" or "unsynchronized" for future server synchronization

   update:

   • users can edit the details of existing vinyl records while offline
   • the changes will be applied to the local database instantly
   • edited records will be marked as "pending" or "unsynchronized" for future server synchronization

   delete:

   • when users delete a vinyl record while offline, it will be removed from the local database right away for responsiveness
   • deleted records will be marked as "pending" or "unsynchronized" for future server synchronization

   when online:

   • the app will initiate a synchronization process with the server
   • pending CRUD operations (create, update, delete) that were made while offline will be sent to the server to ensure consistency

6. App mockup. Eg. using figma.com or sketch.com or something equivalent. The screenshots should be attached to the assignment.

Create

Read/View

Update & Delete