I recheck and I think the documentation fooled you. The definition provided in TMF620 must be inaccurate:
This attribute exist in both "Catalog" and "ProductCatalog" resources.
I'm guessing this attribute needs 2 different definitions:
- the "Catalog" entity can have value Product, Service... in field catalogType.
- the "ProductCatalog" entity cannot have value Product, Service... in field
catalogType.
but I don't have any idea what you would put in catalogType
we have needs to associate ProductCatalog with Sales Channels, Market Segments, Customer type, product line etc. but these don't exist in the API.
we used catalogType in our previous BSS to store these values:
- B2B-Web-Telecom
- B2B-telephone-Telecom
- B2C-Web-energy
- etc.
------------------------------
Kind regards,
Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS
------------------------------
Original Message:
Sent: Jun 04, 2025 04:56
From: MMH HH
Subject: How to store resource and service candidates in the catalog?
Thanks @Matthieu Hattab. I had a brain fade for a moment when I looked at that `catalogType` field; I feel like an idiot now. I realise there are totally different APIs for different catalogs. I think we should take out this field from the catalogs. I got the examples from the API user guide (once I realised they are completely different APIs :-))
------------------------------
Manu
Original Message:
Sent: Jun 04, 2025 04:16
From: Matthieu Hattab
Subject: How to store resource and service candidates in the catalog?
The catalog can be product, service and resource and can be identified based on the `catalogType` of the catalog.
As a general high level statement, you could say that, but once you start looking at the details, the 3 API are very different. You cannot take one catalogue API and just change the "catalogType" to make it look like a "resource" or a "product" catalogue.
Take TMF 620, "catalogType" could never be "resource".
If you can share an example of service and/or resource catalog and categories, it would be useful.
I know you know that each API has a user guide and OAS file with examples of catalogue and categories. can you clarify your question?
------------------------------
Kind regards,
Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS
Original Message:
Sent: Jun 03, 2025 17:58
From: MMH HH
Subject: How to store resource and service candidates in the catalog?
The catalog can be product, service and resource and can be identified based on the `catalogType` of the catalog.
Catalog contains categories. It is mentioned that the `Category` can contain product offerings, resource or service candidates. However, as shown in the API request below, there is a reference to `ProductOffering` but no reference to `ResourceCandidate` or `ServiceCandidate`. How do I store resource and/or service candidates if my catalog is resource and/or service catalog.
If you can share an example of service and/or resource catalog and categories, it would be useful.
------------------------------
Manu
------------------------------