aidan-bailey / anidopt Goto Github PK

Services need to be integrated into their respective controllers.

Integrations:

• AnimalsController
• BreedsController
• DescriptorLinksController
• DescriptorsController
• DescriptorTypesController
• EstimationsController
• OrganisationsController
• SexesController
• SpeciesController

Relationships can be defined in the AnidoptContext.cs OnModelCreating method.
Perhaps it would be best to update the database diagrams first.

Animals have colours.

An animal can have one to many colours.

Basic services for tables need to be implemented.
Each service must have an interface and an implementation.
Services must be registered in the dependency injection registry.

Basic methods:

• bool Initialised { get; }
• Task<List<[Type]>> Get[Type]sAsync();
• Task<[Type]?> Get[Type]ByIdAsync(int id);
• Task<bool> [Type]ExistsByIdAsync(int id);
• Task Ensure[Type]DeletionByIdAsync(int id);

Services:

• AnimalService
• BreedService
• DescriptorService
• DescriptorLinkService
• DescriptorTypeService
• EstimationService
• OrganisationService
• SexService
• SpeciesService

Description

Users need to be able to login and view different things based on them.

Notes

• There are two types of users: Admin and Organisation
• Admins should be able to see and edit all the database tables.
• Organisations should be able to see and edit their animals.

TODO

I like the idea of the Site Admin having unfettered access over the database tables.

Right now I set up the Entity controllers expecting average users to use them, now I am not so sure.
I think the current Entity controllers should be used strictly by Site Admins.
The views and controllers should be reworked so they can directly edit the database as is without any abstractions (so no fancy link-proxy nonsense).

Description

Animals need pictures!

Notes

• Pictures will be stored in the database.
• Size of pictures will currently just be 2GB as that is the maximum size of a VARBINARY field.
• Each animal can have zero to many pictures with zero to one main picture selected (to be displayed on the grid card).
• The picture table will have the schema: (Id: int, Bytes: ByteArray, AnimalId: int, Main: bool).

TODO

• Create picture table.
• Create picture service.
• Create picture controller/views.
• Add to Animal controller/view.

An Organisation Admin should be able to do several things:

• View own profile
• Edit own profile
• View Organisation Users
• Create Organisation Users
• Edit Organisation Users
• Remove Organisation Users
• View Classifieds
• Create Classifieds
• Edit Classifieds
• Remove Classifieds