[
https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569413#action_12569413
]
Valentina Sirkova commented on OFBIZ-1590:
------------------------------------------
Thank you very much Jacopo for your comment!
Yes I remember this discussion. Just one clarification-these ideas are based on
the book "Data Model Book" - travel chapter(which i read many, many times :))
and what impressed me there was that Workeffort is not used for rental at all!
Also TechCalendars are not used for that purpose!!
Actually the availability of an item could be checked from an entity called
"ReservationItem".
The interesting thing is tthis book looks at travel orders as usual orders and
therefore we could think of ReservationItem as OrderItem in our system.
This means we will check availability on OrderItem and NOT any of the calendars
or WorkEffort.
On the other hand the TechDataCalendars could be used simply for fixedAsset
maintenance(e.g room maintanance etc)
I believe in this way we achieve logical distinction of manufacturing,
workeffort and rental....What do you think about this Book`s idea?
> 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.
