[jira] Created: (OFBIZ-1590) Introduction of new reservation entities
Locked
12
12
[jira] Created: (OFBIZ-1590) Introduction of new reservation entities
 
|
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 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. |
[jira] Updated: (OFBIZ-1590) Introduction of new reservation entities
|
|
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentina Sirkova updated OFBIZ-1590: ------------------------------------- Attachment: spot_class_map_entities.patch > 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. |
[jira] Commented: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561217#action_12561217 ] Valentina Sirkova commented on OFBIZ-1590: ------------------------------------------ Here http://docs.ofbiz.org/display/OFBIZ/Proposal+for+Plane%2C+Bus%2C+Restaurant+and+Cinema+Seats you can see picutre of these entities. In red dotted lines are the fields I want to extend(add). > 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. |
[jira] Issue Comment Edited: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561217#action_12561217 ] valentina edited comment on OFBIZ-1590 at 1/21/08 8:31 PM: ------------------------------------------------------------------- Here http://docs.ofbiz.org/display/OFBIZ/Proposal+for+Plane%2C+Bus%2C+Restaurant+and+Cinema+Seats you can see picutre of these entities. In red dotted lines are the fields I want to extend(add). In purpule are the original entities from the book. was (Author: valentina): Here http://docs.ofbiz.org/display/OFBIZ/Proposal+for+Plane%2C+Bus%2C+Restaurant+and+Cinema+Seats you can see picutre of these entities. In red dotted lines are the fields I want to extend(add). > 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. |
[jira] Commented: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561639#action_12561639 ] karnchana pangwan commented on OFBIZ-1590: ------------------------------------------ Hi Valentina I extended three entities (with Restaurant reservations) if I want to add booking fee with different class in AccommodationClass How can I do? > 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. |
[jira] Commented: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561656#action_12561656 ] Valentina Sirkova commented on OFBIZ-1590: ------------------------------------------ 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. |
[jira] Issue Comment Edited: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ 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. |
[jira] Updated: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Risaliti updated OFBIZ-1590: ---------------------------------- Component/s: order > 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: 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. |
[jira] Commented: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562394#action_12562394 ] karnchana pangwan commented on OFBIZ-1590: ------------------------------------------ thanks Valentina, Now I created three entities and added new example data and extended workeffort, but I not sure about my data model. In "nrOfSpaces" of AccommodationSpot I added space for person. With my demo provide customer select fixedasset,class and tables number (get accommSpotId into workeffort) and input time for make reservation (restaurant). Can you check it again about my data? and if it work can I commit? My data -------------------------- ?xml version="1.0" encoding="UTF-8"?> <entity-engine-xml> <FixedAsset fixedAssetId="Restaurant" parentFixedAssetId="" fixedAssetName="Restaurant" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Private Rooms" parentFixedAssetId="Restaurant" fixedAssetName="Private Rooms" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Communal tables" parentFixedAssetId="Restaurant" fixedAssetName="Communal tables" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Bar/Lounge" parentFixedAssetId="Restaurant" fixedAssetName="Bar/Lounge" locatedAtFacilityId="Tableservice"/> <AccommodationClass accommClassId="Tables" parAccommClassId="" description="Tables"/> <AccommodationClass accommClassId="VIPTables" parAccommClassId="Tables" description="VIP table"/> <AccommodationClass accommClassId="PartyTables" parAccommClassId="Tables" description="Party Table"/> <AccommodationClass accommClassId="Chairs" parAccommClassId="" description="Chairs"/> <AccommodationMap accommClassId="Tables" fixedAssetId="Restaurant" nrOfSpaces="20" overbooked="0"/> <AccommodationMap accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="3" overbooked="0"/> <AccommodationMap accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="5" overbooked="0"/> <AccommodationMap accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="3" overbooked="0"/> <AccommodationMap accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="5" overbooked="0"/> <AccommodationMap accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="10" overbooked="0"/> <AccommodationSpot accommSpotId="1" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-1"/> <AccommodationSpot accommSpotId="2" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-2"/> <AccommodationSpot accommSpotId="3" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-3"/> <AccommodationSpot accommSpotId="4" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-1"/> <AccommodationSpot accommSpotId="5" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-2"/> <AccommodationSpot accommSpotId="6" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-3"/> <AccommodationSpot accommSpotId="7" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="4" accomNumber="PrVIP-4"/> <AccommodationSpot accommSpotId="8" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="4" accomNumber="PrVIP-5"/> <AccommodationSpot accommSpotId="9" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="4" accomNumber="CmT-1"/> <AccommodationSpot accommSpotId="10" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="4" accomNumber="CmT-2"/> <AccommodationSpot accommSpotId="11" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-3"/> <AccommodationSpot accommSpotId="12" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-4"/> <AccommodationSpot accommSpotId="13" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-5"/> <AccommodationSpot accommSpotId="14" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-1"/> <AccommodationSpot accommSpotId="15" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-2"/> <AccommodationSpot accommSpotId="16" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-3"/> <AccommodationSpot accommSpotId="17" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-1"/> <AccommodationSpot accommSpotId="18" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-2"/> <AccommodationSpot accommSpotId="19" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-3"/> <AccommodationSpot accommSpotId="20" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-4"/> <AccommodationSpot accommSpotId="21" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-5"/> <AccommodationSpot accommSpotId="22" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-6"/> <AccommodationSpot accommSpotId="23" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-7"/> <AccommodationSpot accommSpotId="24" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-8"/> <AccommodationSpot accommSpotId="25" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-9"/> <AccommodationSpot accommSpotId="26" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-10"/> </entity-engine-xml> > 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: 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. |
[jira] Issue Comment Edited: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562394#action_12562394 ] purewing edited comment on OFBIZ-1590 at 1/25/08 12:14 AM: -------------------------------------------------------------------- thanks Valentina, Now I created three entities and added new example data and extended workeffort, but I not sure about my data model. In "nrOfSpaces" of AccommodationSpot I added space for person. With my demo provide customer select fixedasset,class and tables number (get accommSpotId into workeffort) and input time for make reservation (restaurant). Can you check it again about my data? and if it work can I commit? My data -------------------------- <?xml version="1.0" encoding="UTF-8"?> <entity-engine-xml> <FixedAsset fixedAssetId="Restaurant" parentFixedAssetId="" fixedAssetName="Restaurant" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Private Rooms" parentFixedAssetId="Restaurant" fixedAssetName="Private Rooms" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Communal tables" parentFixedAssetId="Restaurant" fixedAssetName="Communal tables" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Bar/Lounge" parentFixedAssetId="Restaurant" fixedAssetName="Bar/Lounge" locatedAtFacilityId="Tableservice"/> <AccommodationClass accommClassId="Tables" parAccommClassId="" description="Tables"/> <AccommodationClass accommClassId="VIPTables" parAccommClassId="Tables" description="VIP table"/> <AccommodationClass accommClassId="PartyTables" parAccommClassId="Tables" description="Party Table"/> <AccommodationClass accommClassId="Chairs" parAccommClassId="" description="Chairs"/> <AccommodationMap accommClassId="Tables" fixedAssetId="Restaurant" nrOfSpaces="20" overbooked="0"/> <AccommodationMap accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="3" overbooked="0"/> <AccommodationMap accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="5" overbooked="0"/> <AccommodationMap accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="3" overbooked="0"/> <AccommodationMap accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="5" overbooked="0"/> <AccommodationMap accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="10" overbooked="0"/> <AccommodationSpot accommSpotId="1" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-1"/> <AccommodationSpot accommSpotId="2" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-2"/> <AccommodationSpot accommSpotId="3" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-3"/> <AccommodationSpot accommSpotId="4" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-1"/> <AccommodationSpot accommSpotId="5" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-2"/> <AccommodationSpot accommSpotId="6" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-3"/> <AccommodationSpot accommSpotId="7" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="4" accomNumber="PrVIP-4"/> <AccommodationSpot accommSpotId="8" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="4" accomNumber="PrVIP-5"/> <AccommodationSpot accommSpotId="9" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="4" accomNumber="CmT-1"/> <AccommodationSpot accommSpotId="10" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="4" accomNumber="CmT-2"/> <AccommodationSpot accommSpotId="11" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-3"/> <AccommodationSpot accommSpotId="12" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-4"/> <AccommodationSpot accommSpotId="13" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-5"/> <AccommodationSpot accommSpotId="14" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-1"/> <AccommodationSpot accommSpotId="15" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-2"/> <AccommodationSpot accommSpotId="16" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-3"/> <AccommodationSpot accommSpotId="17" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-1"/> <AccommodationSpot accommSpotId="18" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-2"/> <AccommodationSpot accommSpotId="19" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-3"/> <AccommodationSpot accommSpotId="20" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-4"/> <AccommodationSpot accommSpotId="21" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-5"/> <AccommodationSpot accommSpotId="22" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-6"/> <AccommodationSpot accommSpotId="23" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-7"/> <AccommodationSpot accommSpotId="24" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-8"/> <AccommodationSpot accommSpotId="25" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-9"/> <AccommodationSpot accommSpotId="26" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-10"/> </entity-engine-xml> was (Author: purewing): thanks Valentina, Now I created three entities and added new example data and extended workeffort, but I not sure about my data model. In "nrOfSpaces" of AccommodationSpot I added space for person. With my demo provide customer select fixedasset,class and tables number (get accommSpotId into workeffort) and input time for make reservation (restaurant). Can you check it again about my data? and if it work can I commit? My data -------------------------- ?xml version="1.0" encoding="UTF-8"?> <entity-engine-xml> <FixedAsset fixedAssetId="Restaurant" parentFixedAssetId="" fixedAssetName="Restaurant" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Private Rooms" parentFixedAssetId="Restaurant" fixedAssetName="Private Rooms" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Communal tables" parentFixedAssetId="Restaurant" fixedAssetName="Communal tables" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Bar/Lounge" parentFixedAssetId="Restaurant" fixedAssetName="Bar/Lounge" locatedAtFacilityId="Tableservice"/> <AccommodationClass accommClassId="Tables" parAccommClassId="" description="Tables"/> <AccommodationClass accommClassId="VIPTables" parAccommClassId="Tables" description="VIP table"/> <AccommodationClass accommClassId="PartyTables" parAccommClassId="Tables" description="Party Table"/> <AccommodationClass accommClassId="Chairs" parAccommClassId="" description="Chairs"/> <AccommodationMap accommClassId="Tables" fixedAssetId="Restaurant" nrOfSpaces="20" overbooked="0"/> <AccommodationMap accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="3" overbooked="0"/> <AccommodationMap accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="5" overbooked="0"/> <AccommodationMap accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="3" overbooked="0"/> <AccommodationMap accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="5" overbooked="0"/> <AccommodationMap accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="10" overbooked="0"/> <AccommodationSpot accommSpotId="1" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-1"/> <AccommodationSpot accommSpotId="2" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-2"/> <AccommodationSpot accommSpotId="3" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-3"/> <AccommodationSpot accommSpotId="4" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-1"/> <AccommodationSpot accommSpotId="5" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-2"/> <AccommodationSpot accommSpotId="6" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-3"/> <AccommodationSpot accommSpotId="7" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="4" accomNumber="PrVIP-4"/> <AccommodationSpot accommSpotId="8" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="4" accomNumber="PrVIP-5"/> <AccommodationSpot accommSpotId="9" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="4" accomNumber="CmT-1"/> <AccommodationSpot accommSpotId="10" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="4" accomNumber="CmT-2"/> <AccommodationSpot accommSpotId="11" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-3"/> <AccommodationSpot accommSpotId="12" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-4"/> <AccommodationSpot accommSpotId="13" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-5"/> <AccommodationSpot accommSpotId="14" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-1"/> <AccommodationSpot accommSpotId="15" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-2"/> <AccommodationSpot accommSpotId="16" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-3"/> <AccommodationSpot accommSpotId="17" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-1"/> <AccommodationSpot accommSpotId="18" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-2"/> <AccommodationSpot accommSpotId="19" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-3"/> <AccommodationSpot accommSpotId="20" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-4"/> <AccommodationSpot accommSpotId="21" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-5"/> <AccommodationSpot accommSpotId="22" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-6"/> <AccommodationSpot accommSpotId="23" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-7"/> <AccommodationSpot accommSpotId="24" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-8"/> <AccommodationSpot accommSpotId="25" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-9"/> <AccommodationSpot accommSpotId="26" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-10"/> </entity-engine-xml> > 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: 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. |
[jira] Issue Comment Edited: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562394#action_12562394 ] purewing edited comment on OFBIZ-1590 at 1/25/08 12:36 AM: -------------------------------------------------------------------- thanks Valentina, Now I created three entities and added new example data and extended workeffort, but I not sure about my data model. In "nrOfSpaces" of AccommodationSpot I added space for person. With my demo provide customer select fixedasset,class and tables number (get accommSpotId into workeffort) and input time for make reservation (restaurant). Can you check it again about my data? My data -------------------------- <?xml version="1.0" encoding="UTF-8"?> <entity-engine-xml> <FixedAsset fixedAssetId="Restaurant" parentFixedAssetId="" fixedAssetName="Restaurant" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Private Rooms" parentFixedAssetId="Restaurant" fixedAssetName="Private Rooms" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Communal tables" parentFixedAssetId="Restaurant" fixedAssetName="Communal tables" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Bar/Lounge" parentFixedAssetId="Restaurant" fixedAssetName="Bar/Lounge" locatedAtFacilityId="Tableservice"/> <AccommodationClass accommClassId="Tables" parAccommClassId="" description="Tables"/> <AccommodationClass accommClassId="VIPTables" parAccommClassId="Tables" description="VIP table"/> <AccommodationClass accommClassId="PartyTables" parAccommClassId="Tables" description="Party Table"/> <AccommodationClass accommClassId="Chairs" parAccommClassId="" description="Chairs"/> <AccommodationMap accommClassId="Tables" fixedAssetId="Restaurant" nrOfSpaces="20" overbooked="0"/> <AccommodationMap accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="3" overbooked="0"/> <AccommodationMap accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="5" overbooked="0"/> <AccommodationMap accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="3" overbooked="0"/> <AccommodationMap accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="5" overbooked="0"/> <AccommodationMap accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="10" overbooked="0"/> <AccommodationSpot accommSpotId="1" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-1"/> <AccommodationSpot accommSpotId="2" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-2"/> <AccommodationSpot accommSpotId="3" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-3"/> <AccommodationSpot accommSpotId="4" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-1"/> <AccommodationSpot accommSpotId="5" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-2"/> <AccommodationSpot accommSpotId="6" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-3"/> <AccommodationSpot accommSpotId="7" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="4" accomNumber="PrVIP-4"/> <AccommodationSpot accommSpotId="8" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="4" accomNumber="PrVIP-5"/> <AccommodationSpot accommSpotId="9" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="4" accomNumber="CmT-1"/> <AccommodationSpot accommSpotId="10" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="4" accomNumber="CmT-2"/> <AccommodationSpot accommSpotId="11" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-3"/> <AccommodationSpot accommSpotId="12" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-4"/> <AccommodationSpot accommSpotId="13" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-5"/> <AccommodationSpot accommSpotId="14" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-1"/> <AccommodationSpot accommSpotId="15" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-2"/> <AccommodationSpot accommSpotId="16" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-3"/> <AccommodationSpot accommSpotId="17" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-1"/> <AccommodationSpot accommSpotId="18" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-2"/> <AccommodationSpot accommSpotId="19" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-3"/> <AccommodationSpot accommSpotId="20" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-4"/> <AccommodationSpot accommSpotId="21" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-5"/> <AccommodationSpot accommSpotId="22" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-6"/> <AccommodationSpot accommSpotId="23" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-7"/> <AccommodationSpot accommSpotId="24" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-8"/> <AccommodationSpot accommSpotId="25" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-9"/> <AccommodationSpot accommSpotId="26" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-10"/> </entity-engine-xml> was (Author: purewing): thanks Valentina, Now I created three entities and added new example data and extended workeffort, but I not sure about my data model. In "nrOfSpaces" of AccommodationSpot I added space for person. With my demo provide customer select fixedasset,class and tables number (get accommSpotId into workeffort) and input time for make reservation (restaurant). Can you check it again about my data? and if it work can I commit? My data -------------------------- <?xml version="1.0" encoding="UTF-8"?> <entity-engine-xml> <FixedAsset fixedAssetId="Restaurant" parentFixedAssetId="" fixedAssetName="Restaurant" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Private Rooms" parentFixedAssetId="Restaurant" fixedAssetName="Private Rooms" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Communal tables" parentFixedAssetId="Restaurant" fixedAssetName="Communal tables" locatedAtFacilityId="Tableservice"/> <FixedAsset fixedAssetId="Bar/Lounge" parentFixedAssetId="Restaurant" fixedAssetName="Bar/Lounge" locatedAtFacilityId="Tableservice"/> <AccommodationClass accommClassId="Tables" parAccommClassId="" description="Tables"/> <AccommodationClass accommClassId="VIPTables" parAccommClassId="Tables" description="VIP table"/> <AccommodationClass accommClassId="PartyTables" parAccommClassId="Tables" description="Party Table"/> <AccommodationClass accommClassId="Chairs" parAccommClassId="" description="Chairs"/> <AccommodationMap accommClassId="Tables" fixedAssetId="Restaurant" nrOfSpaces="20" overbooked="0"/> <AccommodationMap accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="3" overbooked="0"/> <AccommodationMap accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="5" overbooked="0"/> <AccommodationMap accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="3" overbooked="0"/> <AccommodationMap accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="5" overbooked="0"/> <AccommodationMap accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="10" overbooked="0"/> <AccommodationSpot accommSpotId="1" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-1"/> <AccommodationSpot accommSpotId="2" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-2"/> <AccommodationSpot accommSpotId="3" accommClassId="PartyTables" fixedAssetId="Private Rooms" nrOfSpaces="30" accomNumber="PrPy-3"/> <AccommodationSpot accommSpotId="4" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-1"/> <AccommodationSpot accommSpotId="5" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-2"/> <AccommodationSpot accommSpotId="6" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="2" accomNumber="PrVIP-3"/> <AccommodationSpot accommSpotId="7" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="4" accomNumber="PrVIP-4"/> <AccommodationSpot accommSpotId="8" accommClassId="VIPTables" fixedAssetId="Private Rooms" nrOfSpaces="4" accomNumber="PrVIP-5"/> <AccommodationSpot accommSpotId="9" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="4" accomNumber="CmT-1"/> <AccommodationSpot accommSpotId="10" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="4" accomNumber="CmT-2"/> <AccommodationSpot accommSpotId="11" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-3"/> <AccommodationSpot accommSpotId="12" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-4"/> <AccommodationSpot accommSpotId="13" accommClassId="Tables" fixedAssetId="Communal tables" nrOfSpaces="6" accomNumber="CmT-5"/> <AccommodationSpot accommSpotId="14" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-1"/> <AccommodationSpot accommSpotId="15" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-2"/> <AccommodationSpot accommSpotId="16" accommClassId="VIPTables" fixedAssetId="Communal tables" nrOfSpaces="10" accomNumber="CmVIP-3"/> <AccommodationSpot accommSpotId="17" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-1"/> <AccommodationSpot accommSpotId="18" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-2"/> <AccommodationSpot accommSpotId="19" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-3"/> <AccommodationSpot accommSpotId="20" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-4"/> <AccommodationSpot accommSpotId="21" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-5"/> <AccommodationSpot accommSpotId="22" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-6"/> <AccommodationSpot accommSpotId="23" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-7"/> <AccommodationSpot accommSpotId="24" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-8"/> <AccommodationSpot accommSpotId="25" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-9"/> <AccommodationSpot accommSpotId="26" accommClassId="Chairs" fixedAssetId="Bar/Lounge" nrOfSpaces="1" accomNumber="brc-10"/> </entity-engine-xml> > 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: 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. |
[jira] Updated: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] karnchana pangwan updated OFBIZ-1590: ------------------------------------- Comment: was deleted > 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: 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. |
[jira] Commented: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562548#action_12562548 ] Valentina Sirkova commented on OFBIZ-1590: ------------------------------------------ Hi Karnchana, Let`s move this discussion to the user list(subscribe if you have not). I created a thread with your comments. Here is the link: http://www.nabble.com/Question-on-spot-class-map-entities%28copied-from-jira-1590%29-to15089930.html Regards: 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: 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. |
[jira] Commented: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563657#action_12563657 ] Valentina Sirkova commented on OFBIZ-1590: ------------------------------------------ I am uploading enhanced and improved version of the patch(second version). This improvement is based on David`s comments with numbers: 1, 4a and 5 here: http://www.nabble.com/Re%3A-new-accomodation-map-entities-Jira-OFBIZ-1590-%28was-on-the-user-mailing-list%29-to15128518.html To summarize the second version of the patch: - new entity AccommodationMapType is added with fields accommodationMapType which is pk and description field. AccommodationMap entity is extended with accommodationMapType field to support relationship to the new entity. AccommodationMap entity relates to AccommodationMapType through relationship of type "one". - names of the fields are now fluent and more clear, based on the coding conventions. - these entities are moved to the FixedAsset`s package. > 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: 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. |
[jira] Updated: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentina Sirkova updated OFBIZ-1590: ------------------------------------- Attachment: spot_class_map_entities.patch > 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: 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. |
[jira] Updated: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-1590: ------------------------------- Attachment: accomProgram.patch > 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. |
[jira] Updated: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-1590: ------------------------------- Attachment: accomEntity.patch entity definitions > 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. |
[jira] Commented: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569163#action_12569163 ] Hans Bakker commented on OFBIZ-1590: ------------------------------------ I have added 2 patch files: 1. entity patch to add the new accomodation map,spot class and mapType and add these to the workeffort to enable the reservation 2. order program changes to allow for the reservation of an accomodation spot on a accomodation map. IE a certain table in a restaurant or a rownumber/seatnumber in a cinema. the entities have slightly changed: instead of using the key class/fixedassetId on the accomodation map we still have these fields but now use a accomodationMapId as the key only to simplyfy things. If no objections I will commit these 2 patches in the next few days. > 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. |
[jira] Commented: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569379#action_12569379 ] Valentina Sirkova commented on OFBIZ-1590: ------------------------------------------ Hans, First of all, thanks for caring for the entities. I have 2 questions and two comments. Here are the questions(I asked it a lot of times but never got an answer. I hope this time you will answer): 1. Why do you extend the Workeffort entity? I guess it is the easier way to go as the current OFBiz implementation supports it but this is not the BOOK-BASED approach, but a big FIX! 2. While we are at this stage of development why don`t we stop for a while and think what is BEST for the PROJECT and even if necessary IMPROVE the current implementation with the BOOK`s one? Here is short comparison of the entities involved in current OFBiz reservation implementation and the BOOK`s proposal: Current OFBiz entities: (1)OrderHeader - (2)OrderItem - (3)WorkOrderItemFullFillment - (4)WorkEffort - (5)TechDataCalendar - (6)TechDataExcDay - ((7) TechDataCalWeek) - entity number (3) is of no real use! It is just a connection to the Workeffort. - entities number (5),(6),(7) keep the same information as the workeffort. BOOK`s entities: (This is based on my comprehention of Reservation and ReservationItem from the book. I believe their logical model in our OFBiz db are OrderHeader and OrderItem. Please correct me if I am wrong!) (1)OrderHeader(Reservation) - (2)OrderItem(ReservationItem) Isn`t the book`s way better? > 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. |
[jira] Commented: (OFBIZ-1590) Introduction of new reservation entities
|
|
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569385#action_12569385 ] Valentina Sirkova commented on OFBIZ-1590: ------------------------------------------ Here is the first comment. 1. I do not understand why you have cut the relationship of the AccommodationMap to the AccommodationSpot? What are the reasons for that? I really don`t understand.? 2. You have removed my extended field "overbooked" for storing overbooking data in AccommodationMap. Where do you think of placing it? I did not see it anywhere in the patches. 3. Also I noticed you have not extended ShoppingListItem with spot and map fields. 4. Why do you extend all entities with mapId field??? Isn`t it enough to use the spotId field only?? If you keep these two entities related you just need the spot i guess... 5. In Spot entity you use nrOfSpaces, while it was suggested to use numberOfSpaces. > 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. |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |