On 02 Oct 09:55, Chris Larsen wrote:
> On Thursday, 2 October 2014 18:33:59 UTC+3, Chris Larsen wrote:
> >
> > Dear All,
> >
> > I stumbled across an interesting issue when setting up product categories 
> > for biomedical equipment: 
> >
> > If you look at the 2011 WHO Core Medical Equipment 
> > <http://apps.who.int/iris/bitstream/10665/95788/1/WHO_HSS_EHT_DIM_11.03_eng.pdf>
> >  
> > documentation, there is, for instance, a product category called:
> >
> > "Analyzer, Laboratory, Hematology, Blood Grouping, Automated", which can 
> > be translated nicely into a category tree.
> > However, there are currently two "standards", UMDNS and GMDN, that mean 
> > the same, yet have different naming conventions, plus give a code to each 
> > of their very own terms. Example:
> >
> > UMDNS equivalent: Analyzers, Laboratory, Hematology, Blood Grouping, 
> > Automated
> > UMDNS code: 16817
> >
> > GMDN equivalent: ABO/Rh(D) Blood Grouping Analyser IVD, Automated
> > GMDN code: 56712
> >
> > That is close enough for aliases of a given category term, but we also 
> > need a fields for the respective standards' codes.
> >
> > Would it be possible to attach the attribute and attribute categories 
> > facility to the product categories, so that for each category we could 
> > define aliases and coses for each alas, PLUS a code for the category term 
> > itself?
> >
> > I would otherwise see some serious issue in using Tryton for 
> > "standardised" products, especially, if there are several "standards" 
> > competing with each other, as is often seen in high-value environments, 
> > such as health.
> >
> > Any thoughts?

Product Category in Tryton is mainly done for accounting purpose.
If you need more categories tree, it is better to create a new tree
structure for it.
But maybe we could have in base a "category" like the one on party (and
probably rename the current one as accounting category/group).

> An add-on, related: 
> I noted that in the Product Categories section, I can sort only by Name in 
> the left-hand column showing the ends of each branch of the category tree. 

Yeps, it is not possible right now to do better. Maybe when WITH
statement will be implemented in python-sql.

> The 2nd column showing the whole tree is not sort-able at all, yet it 
> should to cope with complex trees. 
> Am is missing something? Thanks a lot,

No, it is not because it is not possible right now.

-- 
Cédric Krier - B2CK SPRL
Email/Jabber: [email protected]
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

Attachment: pgpr4zfFSzGpf.pgp
Description: PGP signature

Reply via email to