From/Thru date for catalog

[Wai]

Is there currently a way to delete or expire catalogs?

If not, would it be useful to add From/Thru fields in the ProdCatalog entity?

Thanks
Wai

[Ankush Upadhyay]

Hello,
You can expire the catalogs from store by using ProductStoreCatalog entity.



On 05/29/2012 04:46 AM, Wai wrote:

> Is there currently a way to delete or expire catalogs?
>
> If not, would it be useful to add From/Thru fields in the ProdCatalog
> entity?
>
> Thanks
> Wai
>
> --
> View this message in context: http://ofbiz.135035.n4.nabble.com/From-Thru-date-for-catalog-tp4632586.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.

--
Thanks&  Regards
Ankush Upadhyay
[hidden email]

[Wai]

ProductStoreCatalog entity provides store, catalog applicability.  The From/Thru field provide a way to expire this association.  But it does not give any indication that a particular catalog is no longer of use for a business.

Over the years, catalogs are created and retired.  Hence, catalogs for different purposes are accumulated over the years.  I'm more referring to a catalog that is no longer of use for business purposes and need to be retired and/or deleted.

So back to the original question.  Does it make sense to implement a From/Thru date for the entity ProdCatalog?

Thanks,
Wai

[Ashish Vijaywargiya-5]

Hello Wai,

Think a scenario in which one catalog is associated with multiple
Product Store. In that case the solution that you are proposing will not
be a feasible solution. Thanks!

--
Kind Regards
Ashish Vijaywargiya
HotWax Media - est. 1997


On Tuesday 29 May 2012 04:09 PM, Wai wrote:
> So back to the original question.  Does it make sense to implement a
> From/Thru date for the entity ProdCatalog?

[Wai]

Even though a catalog can be used by multiple stores.  I do not see how it is not feasible from an operational point of view.

If a catalog is expired because it is no longer applicable (eg. last summer's product line).  Retiring a catalog should be reflected in all stores using the catalog.  All stores making use of the retired catalog should first verify that the catalog is active for the store in addition to verifying that the catalog is indeed active.  If the catalog is found to be expired, ofbiz would hide the retired catalog from selection at the visitor's store (or website).

This offers a central point for management of catalogs.

Wai

[Jacques Le Roux]

Yes I tend to agree with Wai, I don't see any reason to not have those fields. Now if there is no code at all associated with them I
don't see either any reasons to add them OOTB.

In other words, please use your own way in your customised application or/and contribute.

Jacques

From: "Wai" <[hidden email]>

> Even though a catalog can be used by multiple stores.  I do not see how it is
> not feasible from an operational point of view.
>
> If a catalog is expired because it is no longer applicable (eg. last
> summer's product line).  Retiring a catalog should be reflected in all
> stores using the catalog.  All stores making use of the retired catalog
> should first verify that the catalog is active for the store in addition to
> verifying that the catalog is indeed active.  If the catalog is found to be
> expired, ofbiz would hide the retired catalog from selection at the
> visitor's store (or website).
>
> This offers a central point for management of catalogs.
>
> Wai
>
> --
> View this message in context: http://ofbiz.135035.n4.nabble.com/From-Thru-date-for-catalog-tp4632586p4632870.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.