jimmyson / beepbong Goto Github PK

To save on data transmission, logo images would need to be modified prior to being written to the Database.
Images larger than 720px high need to be scaled to this resolution, keeping image ratio in-tact.

Ignore the need to stretch or compress images on width. Currently expecting user to handle this.

Due to poor practices and manual testing, Test coverage needs to expand to ensure a stable piece of software.
Users would want to be ensured that the platform will not break under use, or break the rules when performing operations

Outside of Guid checks, there is no duplication checking on Names and Attributes of entities.
To prevent duplicate records. Database checking on these properties needs to be expanded upon.

Improve usability of Programme Index screen by reducing displayed content with pagination.

Expecting many entites to be created, and infinate scroll will cause page loading issues when accounting for Images and lots of items.
Helps reduce work on pulling information from the Database.

Describe the solution you'd like
A dynamic UI component that can be modulated into components.
Dashboard-like display, and easy navigation.

Additional context

Is your feature request related to a problem? Please describe.
There is currently a limitation on how child entities are create on a record.

Describe the solution you'd like
A way to spawn multiple child record to one parent on a single screen without having to create and manually enter in the details each time.

Describe alternatives you've considered
Utilizing KnockoutJS or JavaScript based platforms could allow easy and quick manipulation of the view model before passing to the back end code.
Also consider using Blazor due to the C# back-end, possible utilization for AcoustID.Net and a MediaInfo library to run on the front-end. And a possible skill growth

Whilst storing images in the database is cool and all, it adds more bandwidth to the data being sent each time a page is called, and the image is not cached.

Therefore the image should be written to disc.
Consider leaving the image written to the XML in Base64 for migration.

Is your feature request related to a problem? Please describe.
When updating the model, I am frustrated by having to manually drop the database each time.
The process of migrating at present is the following

1. Extract out the data
2. Drop Database
3. Current Migration Implementation
4. Create New Migration Implementation
5. Create New Database
6. Modify Import Script
7. Import old data

Describe the solution you'd like
The migration process need to export data due, to ensure old information is in tact and not lost.
Modifications need to play friendly with SQLite. This includes creating staging tables. Dropping old tables and constructing the new tables with relevant relationships

Describe alternatives you've considered
Alternatives could be considering is used another SQL management system, due to how Entity Framework is able to alter tables with the Data Connection libraries for SQL Server and MariaDB.

Is your feature request related to a problem? Please describe.
I am frustrated by the mix of samples that are uploaded to the system, I would like to know if a sample fingerprint already exists in the system.

Describe the solution you'd like
MusicBrainz utilises a simple platform called AcoustID that identfies this fingerprint.
A C# library exists under the .NET Framework that can be leveraged here.

Describe the bug
Duplicate records are being created when using the XML Import tool after a previous import.

To Reproduce
Run the XML importer with the same file twice

Expected behavior
The imported should check to see if the entity already exists based on a small selection of properties

• Programme Name
• Channel
• Broadcaster

Is your feature request related to a problem? Please describe.
Concerned than the database is open to malicious modifications to the dataset.

Describe the solution you'd like
A simple user management system that accepts user accounts by email.
Create, Edit and Delete functions are locked behind the user session platform.

Describe alternatives you've considered
Possible to consider using the ASP.Net Identity functionality

Additional context
None as of yet....

Create a Docker container for the application.

https://developer.snapappointments.com/bootstrap-select/

Consider creating a HTML helper item to build the SelectPicker to ensure consistency when implementing the SelectPicker