[
https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569511#action_12569511
]
Hans Bakker commented on OFBIZ-1590:
------------------------------------
Valentina,
First of all thank you for the valuable comments and you interest in this
development.
As you perhaps know this project is customer driven so development is normally
started with a customer request. I am currently working with a customer who
wants to receive reservations for a restaurant. The patches I have supplied
reflect this and these patches are a working implementation.
So about your comments, first comment:
1. Overbooked field: as long as we have no code yet to use this field can wait
until that is available?
2. shopping list: are you sure that reservations will be used in the shopping
list? You have a customer who wants to use that?
3. sure, no problem my error, we will change from nrOfSpaces to numberOfSpaces
Your second comment:
1. Duplication of data:(Workeffort and TechDataCal entities): I completly agree
with that. If the customer wants to use this facility we will try to change
that so it uses workeffort and not techdatacalendar.
2. I agree with that too, although i do not know how to implement that.
3. With this change the seat number problem is solved, and sure we need could
use it for room numbers too.
4. I agree, but how to implement?
5. Using the workeffort and not techdata calendar would solve this problem.
Your last comment:
please remember the workeffort is very good for his purpose: it is used for
reservations AND for maintenance so a room cannot be booked for maintenance AND
reservation.
How about moving forward now, implement the existing 2 patches with the
numberOfSpaces field name changed and starting on the other changes?
Regards,
Hans
> 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.
