[
https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569518#action_12569518
]
Valentina Sirkova commented on OFBIZ-1590:
------------------------------------------
Hans, thanks for your fast reply
I guess I have a clearer picture of your vision now.
About presenting the room types as classes-I have idea how that could be
implemented. Well for this sort of algorithms we will need to extend the
WorkEffort with accommodationClassId field.
About the children and adults, I also have an idea about that and which is
almost finished and i get more time will try to discuss it with the community
There are a few more things I do not understand from the patches you provide.
A.) Why do you extend all entities wth map field? Could you (if you have)
provide demo and seed data so we can better understand you way?I dont see the
purpose of the map field in the workeffort and other entities.
B) Looking at the WorkEffort entity i see it has most of the fields needed for
basing hourly reservation algorithm. However if we (as you agreed) choose to
make the room types classes we will need to extend the workeffort with the
accommodationClassId field(my implementation which i would like to share is
based on that). What do you think about that, are you ok with such idea?
(i hope the answers to these questions(A and B) will clear all ambiguities i
have around your ideas)
Waiting for your response:Valentina
> Introduction of new reservation entities
> ----------------------------------------
>
> Key: OFBIZ-1590
> URL: https://issues.apache.org/jira/browse/OFBIZ-1590
> Project: OFBiz
> Issue Type: Improvement
> Components: order
> Affects Versions: SVN trunk
> Reporter: Valentina Sirkova
> Attachments: accomEntity.patch, accomProgram.patch,
> spot_class_map_entities.patch, spot_class_map_entities.patch
>
>
> I propose the introduction of the following entities: AccommodationClass,
> AccommodationSpot,AccommodationMap. Their design is based on the book "The
> data model resource book".
> - AccommodationClass could define classes for hotels, cars, planes etc. I
> have added one more field here parentAccClass, as I thought it could be
> valuable for building more complicated hierarchies.
> - AccommodationMap is used to say how many spaces a class has. I have
> extended it further with a field overbooked, which could store the
> overbooking data for each class. E.g if we have that field we might know how
> many rooms of class "deluxe" could be overbooked. The primary key of
> AccommodationMap in the book includes the "NrOfSpaces" field but I did not
> add it in the patch as I am not sure of its exact purpose.
> - AccommodationSpot defines the specific seat,room etc of a given class. It
> is very powerful entity as it let us define the seat as a spot simply. This
> is very useful for planes and buses for example as we have the chance to
> define all the seats as spots and are not required to make them fas. I have
> modified the type of the field "accomNumber" to be of type short-varchar as
> plane seats for example are mixture of letters and numbers(The book models it
> of type numeric). The fk fields include the "nrOfSpaces" field in the book
> which I have not included in my patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
