We encourage data partners to provide 3D content following the steps on the page below. Doing so enhances data quality and reusability while contributing to the evaluation and validation of the 3D profile. Following the EDM Mapping Guidelines continues to be mandatory: for example awarding the correct rights statement is of vital importance and influences the tier calculation.

Each step includes a mapping example, showing how the provision evolves and builds on the previous step towards the final mapping. The last example compiles all the steps into a complete example.

Provide the oEmbed URL for the embeddable view of the 3D object as edm:isShownBy. The web resource representation for this view must follow the EDM profile for embeddable resources and meet its requirements.

If more viewers for this object are available and you would like to provide them as alternative views, you can link to each of the viewers using edm:hasView.

Example:

Europeana cannot generate a thumbnail directly from the embedded resource. Therefore, it is strongly recommended that you provide a thumbnail following the instructions indicated in the EDM profile for embeddable resources.

Example:

Provide a direct link to the 3D model as a edm:WebResource. Instances of edm:WebResource that describe corresponding models and views must be connected by a dcterms:isFormatOf relation, where the edm:WebResource for the view references the edm:WebResource for the model (see the second example below).
Consider carefully if the model is suitable for online display, or if it should only be available for users to download. A model that is intended for online display must be linked from the ore:Aggregation with either edm:isShownBy or edm:hasView, while a model intended for downloading only, must not be linked from the ore:Aggregation,

Example of a model suitable for online display:

Example of a model provided for download:

Identify and specify what the intended use (motivation) of the data provider was when digitising the 3D object. This can be provided using the edm:intendedUsage property. The values for the edm:intendedUsage property are controlled and can be found here. Please use a value from the vocabulary at the most granular level. For example, if the intended usage is ‘Research’, use ‘Research’ as a value and not ‘Knowledge’. Only if there is no decision made for the most granular level, then using the intended usage at the higher level is recommended.

If there was no intended use, then data providers SHOULD not use this property.

Example:

Determine whether the model is the result of a 3D digitisation of an object, a reconstruction of an existing one or a digitally created 3D object.

This can be provided using the schema:digitalSourceType property with one of the following controlled values (see further information about them here):

• reality captured: https://cv.iptc.org/newscodes/digitalsourcetype/digitalCapture

• 3D reconstruction: https://cv.iptc.org/newscodes/digitalsourcetype/dataDrivenMedia

• born digital: https://cv.iptc.org/newscodes/digitalsourcetype/digitalCreation

Example:

Multiple properties were already available in the EDM guidelines on the edm:WebResource level to provide context and information on your digital representation. In addition, certain extra properties have now been enabled on the edm:WebResource level as well.

• dc:title: different from the title of the CHO.

• dc:language: the model contains textual descriptions or speech in a specific language.

• dcterms:temporal: the model captures the state of the real-world object during a particular period in time.

Example:

Choose one of the four options from a controlled list vocabulary, and provide it as a reference in dc:type:

• 3D mesh: http://data.europeana.eu/vocabulary/modelType/3DMesh

• 3D point cloud: http://data.europeana.eu/vocabulary/modelType/3DPointCloud

• Building Information Model (BIM): http://data.europeana.eu/vocabulary/modelType/BIM

• Parametric model: http://data.europeana.eu/vocabulary/modelType/parametricModel

The following technical metadata properties can be provided for each type:

Example:

Paradata is information about the process of digitisation of the 3D object. It can take many different forms. Data partners can provide certain paradata using the properties that are currently available on the edm:WebResource level as described in the EDM guidelines and in step 6 on this page.

Alternatively, data partners can provide a link to a full version of paradata published externally preferably using a domain standard such as CIDOC DIG, CARARE 2.0 (ie. other non-standard formats may be used) - an approach that is comparable to what IIIF's Presentation API enables via its rdfs:seeAlso element.

Provide a reference to the paradata as a link from the model web resource to a separate web resource using the rdfs:seeAlso property. The format of the paradata file is specified using the dcterms:conformsTo property as shown in the example below.

Example: