[
https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561656#action_12561656
]
valentina edited comment on OFBIZ-1590 at 1/23/08 4:34 AM:
-------------------------------------------------------------------
Hi Karnchana,
First of all these three entities are not yet committed/approved, which means
the current OFBiz model does not support them in its reservation logic. If you
do want to use them for reservations then you will have to do one of the
following on your own:
1) Extend workeffort with spotId field as suggested by Hans and use the CURRENT
logic.
2) Read the "Data model resource book" vol 2 and decide how to improve/replace
the current logic with more flexible one.
Personally, I am inclined to the second approach(and I am working on it) but
this should be the community`s decision so it is up to you now.
About the "booking fee" I am not sure which sort of booking you mean. It
depends on how you have modeled your data.
In the general case if you want to sell classes directly without assigning any
rooms/fa then you will need connection to
the product entity. If on the other hand you use preassignation then u might
not need it.
In any case in the CURRENT OFBiz implementation the classes are preented as
products and the products are fixedAssets(which I personally do not think is
the best way as room types are not fixed assets in reallity)
Valentina :)
was (Author: valentina):
Hi Karnchana,
First of all these three entities are not yet committed/approved, which means
the current OFBiz model does not support them in its reservation logic. If you
do want to use them for reservations then you will have to do one of the
following on your own:
1) Extend workeffort with spotId field as suggested by Hans and use the CURRENT
logic.
2) Read the "Data model resource book" vol 2 and decide how to improve/replace
the current logic with more flexible one.
Personally, I am inclined to the second approach(and I am working on it) but
this should be the community`s decision so it is up to you now.
About the "booking fee" I am not sure which sort of booking you mean. It
depends on how you have modeled your data.
In the general case if you want to sell classes directly without assigning any
rooms/fa then you will need connection to
the product entity. If on the other hand you use preassignation then u might
not need it.
In any case in the CURRENT OFBiz implementation the classes are preented as
products and the products are fixedAssets(which I personally do not think is
the best way as room types are not fixed assets in reallity)
> Introduction of new reservation entities
> ----------------------------------------
>
> Key: OFBIZ-1590
> URL: https://issues.apache.org/jira/browse/OFBIZ-1590
> Project: OFBiz
> Issue Type: Improvement
> Affects Versions: SVN trunk
> Reporter: Valentina Sirkova
> Attachments: 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.
