Changelog

The following changes have been implemented in the ContentHub recently (sorted by date in descending order):

14.10.2024

• The GET services of productcontext no longer require a Content-Type to be set.
• The service PUT /notifications/v1/subscription/{subscriptionId} now allows the email to be altered.

06.08.2024

• An update of the XSD schema for ContentHub metadata took place - you cannot add any element from ch namespace after element documentType. Only elements from a different namespace can be placed after ch:documentType.

06.08.2024

• The client can now add an email address when creating a notification subscription. This is the email address where the client wants to be alerted if the endpoint he provided for receiving notifications is not reachable.

15.07.2024

• The search service now supports setting the parameter facets=none to disable the faceting completely, which will reduce the response time. The response will then not contain any information for the possible facets anymore.

05.07.2024

• The services for single document ingestion (POST /ingest/v1/workspaces/{applicationId}/content and PUT /ingest/v1/workspaces/{applicationId}/content/entry) have been reworked. Both services will write the given document into the ContentHub database regardless whether the document did or did not exist before. They will no longer produce an HTTP-400 response (when a document did already exist) respectively an HTTP-404 response (when the document did not exist). With the rework of both services we improved the validation in regard to the document's attachments: a document which if defining images or BLOBs in its metadata must be ingested with all attachments given.

16.04.2024

• Notification service is released. In its current implementation only the JSONv1 format is supported. Service description is here Notification API

03.01.2024

• Documents with the metadata field visible set to false (aka invisible documents) will now be hidden from search results by default. This behavior can be circumvented by incorporating explicitly a search-constraint for the field visible. For instance: visible:false or visible:(true OR false)

29.09.2023

• It is now possible to use the fields fingerprint and idesk.rootId as search constraints.

28.07.2023

• The fingerprints-service (GET /bulk/{application_id}/fingerprints) will now render the id of the latest successfully ingested archive in the first line of the CSV response.

19.06.2023

• In the process of Single Doc Ingest, the entire structure of a document is validated according to the XSD schema.
• Documents for which the structure does not respect the XSD will not be ingested and an error will be thrown.

24.03.2023

• The hot.sold_out field can now be used in a related documents' constrainingQuery.

16.03.2023

• the retrieval-services (GET /content/v1/retrieval, GET /content/v1/retrieval/meta, GET /content/v1/retrieval/baseline, GET /content/v1/retrieval/compount/{part}) now accept the URL-parameters highlightingQuery and if applicable highlightingFields. When given words hit by the highlightingQuery will be wrapped with highlight-elements.

13.03.2023

• Extended the related documents response to also return the documentType.

03.02.2023

• In search-requests snippeting has been reworked and extended:
  • the order of given snippet-locations is now respected and will inpact the order of the generated snippets in the search response.
  • for each single snippet-location a maximum count of snippets can be defined. For instance in count:5,location:(title(count:1),baselineContent) at maximum one snippet will be generated from the title.

04.01.2023

• In search-queries the fields for constraining a search to 'baseline' or 'native' have been revised and work now properly. The search API description was updated.

19.12.2022

• If the chb:preview is not provided by the content producer, it will be automatically generated during the Single Doc Ingest out of the chb:baselineContent element (first 500 characters). In this case the autogenerated attribute from the preview element will be set to true.

09.12.2022

• A new field <hot.sold_out> is now available and can be used as a constraint in search queries.

29.11.2022

• A information how bulk-ingest-archives are supposed to be structured has been added to the Ingest API Description.
• The support for the bulk-ingest-archive-manifest, which did not support blobs has been dropped.
• Bulk-Ingest-Manifest-20221108.xsd is now available as further manifest schema to use in bulk-ingest-archives.

25.11.2022

• Removed the context parameter from the snippeting.
• The snippeting search now supports the numberOfTokens parameter, which is equivalent to the maximum number of tokens (typically words) per matching node that surround the highlighted term(s) in the snippet.

08.11.2022

• A new element <hot:parent_category_id> was introduced for HOT. This is the ID of the parent category which is no longer stored under a second <hot:category_id> element (like described bellow).

28.10.2022

• Removed the limit and the offset parameters from the bulk export request descriptor.
• Added the ID of parent category to the HOT (Haufe Online Training) data. Each document will now have two <hot:category_id> elements, one is the ID of the parent category and the other one is the ID of the subcategory.

21.09.2022

• Fixed a bug in the bulk export component that lead to errors when trying to export documents with many attachments.

02.09.2022

• Added the academic title to the <ch:creator> element in HOT (Haufe Online Training) data. Implemented the new element <hot:author> having the attributes title, forename and surname.
• Updated the list of top products for Haufe Shop.

15.08.2022

• Extended the related documents response to also return the list of packageIds.