tch > inventory

Manuel Gozalbes

The requirements of mupreva.org for cataloguing the collection demand for two separate catalogues/invetories.
The first one for bags/boxes of material from excavations, and the second one for objets. The tch model has the 'objects' section, but not a second one for a more general inventory. Is it posible to clone the tch1 section to create an 'inventory' section? This plan also fits well with the Spectrum standard, where "Inventory" is a sort of preliminar documentation, prior to the "Cataloguing" tasks.

Alex

Yes!, of course, inventory section make sense, I created it with tch200. It is a "clone" of tch1 but I remove the cataloguing and Historical tabs, I thinks that is not relevant fields for an inventory,

The change is done into the ontology:

Dédalo 2024-05-01T19:56:01+02:00 Benimamet

Update your installation to get this change.

Best

Manuel Gozalbes

The list of the inventory section only shows the ID column. Is it only in my installation?
Another question. It seems like this section needs a direct connection with 'catalogue'. Usually happens that items first registered as 'inventory' are later catalogued. It's a connection in both directions. But this solution also affects to 'sets'. Maybe the solution is to connect every tch section under a tag like 'related' heritage, similar to the one already created for inmovable heritage.

Alex

Manuel Gozalbes The list of the inventory section only shows the ID column. Is it only in my installation?

No, it's my fault, the list was not defined..., now it's fixed in ontology:

Dédalo 2024-05-03T16:33:32+02:00 Benimamet

Update your installation to get this fix.

Manuel Gozalbes Maybe the solution is to connect every tch section under a tag like 'related' heritage, similar to the one already created for inmovable heritage.

I can not understand you... are you talking about the menu or are you talking about a field inside tch sections? a field that can call to any tch section as objects, photographs, inventory...

Best

Manuel Gozalbes

I'm talking about a field inside tch sections. It's happens when an object is first assigned with an inventory number, but later is catalogued and has another number in a different section.
But take into account that we need to set another relation between objects <> sets
In the first case it's a relation, in the second is a dependency.