From: "David E Jones" <[EMAIL PROTECTED]>
4. while creating the entities we should also add corresponding seed data, including:
Another area we should think about is camping and related (mobile home, camping caravan/recreational vehicule, etc.). I don't know in US and in other part of the world, but there is a lot of seasonal activity in Europe.
4.a. need an AccommodationTypeMap entity starting with types for Seat Map, and Room Map 4.b. for fixedAssetTypeId we should have Vehicle, Transportation Vehicle, Rental Vehicle, and Hotel
Camping site
4.c. for ProductType we should have a bunch including: 4.c.1. Passenger Transportation Offering and sub types including: Flight Offering, Bus Offering, Train Offering, Ship Offering, Other Offering 4.c.2. misc such as Hotel Offering, Rental Car Offering, Amenities Offering, Other Travel Offering
Camping Offering, (RentalCar Offering should be ok for camping caravan/recreational vehicule, not sure for mobile home which are between home and car) Jacques
4.d. RoleType: Travel Provider (if it's not already there) 5. some refinements in names would be good, like using "numberOfSpaces" instead of something more difficult to read and remember how it is shortened; also accommClassId might as well be accommodationClassId, and parentAccommClassId can be like other entities and just be parentClassId 6. these entities are ONLY for modeling the travel offerings, ie the Products, and other changes/additions will be needed for the Order* and related entities, and for the ShoppingCart and related classes I think that's my main feedback on this... just a few little things... ;) -David On Jan 27, 2008, at 8:58 PM, Hans Bakker wrote:Hi Valentina, thanks for your input. The first thing we have to agree now is the entity definitions. Then later we can see how we do the availability checking. For the good order: Karnchana is working with me here. here was you original proposal from you which is a little modified by me: 1. on the accomodation spot it is perhaps better to use the 'description' field instead of number, to be able to also say: "table in the corner with the nice view"? It still can contain a number. 2. In the accomodation map i do not see the reason for the 'overbooked' field, availability is better kept the the workeffort entity (search the workeffort entity for the specific time and the specific accomodation map/spot) and the number of spaces is available in the accomodation map. 3. should the fixed asset be part of the primaryKey of the accomodation map? let me know why? 4. Should the class be a field in the map? isn't it more a specification of the spot? 5. I did some adjustments to the field types. please let me know what you, and others think about this proposal. <entity entity-name="AccommodationClass" package-name="org.ofbiz.order.reservations" title="Accommodation Class"> <field name="accommClassId" type="id-ne"></field> <field name="parentAccommClassId" type="id"></field> <field name="description" type="description"></field> <prim-key field="accommClassId"/> <relation type="one" fk-name="ACCOMM_CLASS_PAR" title="Parent" rel-entity-name="AccommodationClass"> <key-map field-name="parentAccommClassId" rel-field-name="accommClassId"/> </relation> </entity> <entity entity-name="AccommodationSpot" package-name="org.ofbiz.order.reservations" title="Accommodation Spot"> <field name="accommSpotId" type="id-ne"></field> <field name="accommClassId" type="id"></field> <field name="fixedAssetId" type="id"></field> <field name="nrOfSpaces" type="numeric"></field> <field name="description" type="description"></field> <prim-key field="accommSpotId"/> <relation type="one" fk-name="ACCOM_CLASS" rel-entity-name="AccommodationClass"> <key-map field-name="accommClassId"/> </relation> <relation type="one" fk-name="SPOT_FA" rel-entity-name="FixedAsset"> <key-map field-name="fixedAssetId"/> </relation> <relation type="one-nofk" fk-name="ACCOMM_MAP" rel-entity-name="AccommodationMap"> <key-map field-name="accommClassId"/> <key-map field-name="fixedAssetId"/> </relation> </entity> <entity entity-name="AccommodationMap" package-name="org.ofbiz.order.reservations" title="Accommodation Map"> <field name="accommMapId" type="id-ne"></field> <field name="fixedAssetId" type="id"></field> <field name="nrOfSpaces" type="numeric"></field> <prim-key field="accommMapId"/> <relation type="one" fk-name="ACMD_MAP_FA" rel-entity-name="FixedAsset"> <key-map field-name="fixedAssetId"/> </relation> </entity> Add 2 fields to WorkEffort and to the shoppingcart: <field name="accommMapId" type="id"/> <field name="accommSpotId" type="id"/> -- AntWebsystems.com: Quality OFBiz services for competitive rates.....
