Hi, Please let me introduce myself. My name is Rene and i'm from the Netherlands (Johan Cruijff, Weed, etc). After weeks of struggling to build it myself i finally purchased a license.
I really admire your skills and the DDD concept has kept me from sleeping the last couple of weeks ;-)
I work at an Physical Therapy organization [http://www.fysiophysics.nl]) We have one headoffice/ clinic and around 60 small subclinics across the netherlands. I want to use asp.net zero to administrate employees, clinics, equipment, computers, assigned therapist etc. also i want to create an collaboration platform for the employees/therapist with a wikipedia / faq, instructional video's etc.
Here are my questions, how would u do it? : Employees, all employees are Users, should i extend the user with employee information? extending table AbpUsers. or should i create a seperate entity Employee and link them to users? Employees can have one or more addresses with start, end Employees which are of type "Physicaltherapist" have additional therapistscodes should i use fluent ef with migrator?
Clinics, Clinis are organizational units which have an address, geocoordinates to calculate traveltime and distance for HRM Would you extend organization unit with address, etc. or use a new entity. Clinics have one or more Treatmentrooms, are treatmentrooms organizational units, or new entities? -> same for treatmentrooms must have certain equipment. organizational unit or new..
A lot of questions, i hope you can help me. Thanks in advance,
1 Answer(s)
-
0
First of all, thank you for purchasing AspNet Zero and I'm very glad that you liked it :)
You don't need to create an additional entity if you want. You can just extend User entity (that means AbpUsers table): <a class="postlink" href="https://www.aspnetzero.com/Documents/Extending-Existing-Entities#extending-abstract-entities">https://www.aspnetzero.com/Documents/Ex ... t-entities</a> If you want, you can create a new hierarchy (Employee base class and it's derived classes) and reference to Users table as 1 to 1 relation. It's your design choice, each one has it's own pros and cons.
I would extend OrganizationUnit entity for that (it's not abtrsact, see <a class="postlink" href="https://www.aspnetzero.com/Documents/Extending-Existing-Entities#extending-non-abstract-entities">https://www.aspnetzero.com/Documents/Ex ... t-entities</a> for extending non abstract entities). While it's about your domain, Treatmentrooms seems a different entity to me, because it's different that a Clinic. But you would add a OuType to OU to distinguish it. You can know it better than me since I'm very far to that domain :)
