We actually can’t edit an item’s type/class yet, so I was mostly wondering about the actual
dcterms:type metadata field: those fields are currently send over to Omeka as
dcterms:type (and by default we also map
dcterms:type). Would there be any benefit if we map
dcterms:type to Omeka’s resource class (provided
dcterms:type is set to a RDF class that Omeka knows about)?
Once Tropy’s type can be set via the UI we’ll definitely follow the approach you’ve outlined above; but until then, would it be better to map
dcterms:type to the resource class? Personally, I feel like it would be better to stick to the current behavior, just sending
dcterms:type over as
dcterms:type, but the OP made me wonder if there would be some benefit from adding a way to map this to the resource class instead.