Project

General

Profile

« Previous | Next » 

Revision 39177

documentation details

View differences:

webapps/dnet-basic-aggregator/trunk/PROPERTIES.md
196 196
        <td>services.transformation.defaulttemplate</td>  <td>/eu/dnetlib/data/collective/transformation/engine/template.xsl</td>  <td>/eu/dnetlib/data/collective/transformation/engine/template.xsl,/eu/dnetlib/data/collective/transformation/engine/oaftemplate.xsl</td> <td>Template for the Transformator Service.  Two options are available: one for DMF, one for OAF. The schema property above must be set accordingly.</td>
197 197
    </tr>
198 198
    <tr>
199
        <td>services.transformation.vocabularyproperties.json </td>  <td>{"map":{"AccessRights":{"name":"dnet:access_modes", "caseSensitive":"false"}, "Languages":{"name":"dnet:languages", "caseSensitive":"false", "delimiter":"/"}, "TextTypologies":{"name":"dnet:publication_resource", "caseSensitive":"false"}}} applicationContext-transformation.properties
200
{"map":{"AccessRights":{"name":"dnet:rights", "caseSensitive":"false", "delimiter":"/"}, "Languages":{"name":"dnet:languages", "caseSensitive":"false", "delimiter":"/"}, "TextTypologies":{"name":"dnet:texttypologies", "caseSensitive":"false", "delimiter":"/"}}}</td>  <td>json map</td> <td>Instructs the Transformator Service about the D-Net vocabularies to apply for specific fields</td>
199
        <td>services.transformation.vocabularyproperties.json </td>  <td>{"map":{"AccessRights":{"name":"dnet:rights", "caseSensitive":"false", "delimiter":"/"}, "Languages":{"name":"dnet:languages", "caseSensitive":"false", "delimiter":"/"}, "TextTypologies":{"name":"dnet:texttypologies", "caseSensitive":"false", "delimiter":"/"}}}</td>  <td>json map</td> <td>Instructs the Transformator Service about the D-Net vocabularies to apply for specific fields</td>
201 200
    </tr>
202 201
</table>
203 202

  
......
366 365
         </code>
367 366
</td> <td>json map</td> <td>information about the Solr instance to be used. See Solr documentation for details</td>
368 367
    </tr>
369
</table>
370

  
371

  
372

  
373

  
374

  
375

  
376

  
377

  
378

  
379

  
368
</table>
webapps/dnet-basic-aggregator/trunk/README.md
160 160

  
161 161
#Using D-Net
162 162

  
163
Under the root folder of the project you can find the folder <code>mock-repository-content</code>. 
164
It contains 150 oai_dc metadata records you can use to test the functionality of the D-Net software with a Mock Datasource.
163
Under the root folder of the project you can find the folder `mock-repository-content`. 
164
It contains 150 `oai_dc` metadata records you can use to test the functionality of the D-Net software with a Mock Datasource.
165 165

  
166 166
* Place the folder in a location that is readable from tomcat 
167 167
* Start the container
168
* Access the Admin UI (http://${container.hostname}:${container.port}/${container.context}/mvc/ui/index.do)
169
	* If you are running via the maven tomcat plugin with the default properties the URL is: http://localhost:8280/app/mvc/ui/index.do
168
* Access the Admin UI (`http://${container.hostname}:${container.port}/${container.context}/mvc/ui/index.do`)
169
  * If you are running via the maven tomcat plugin with the default properties the URL is: `http://localhost:8280/app/mvc/ui/index.do`
170 170
* Go on Datasource Management --> Overview and search for "mock"
171 171
* Click on "Add metaworkflow" and select the "Collection and Transformation" meta-workflow. This action will associate a meta-workflow (i.e., a workflow of workflows) to the datasource and will create all needed metadata stores.
172
* Click on the "access params" button on the top right and change the base url to the location where you saved the sample folder (e.g. file:///dnet/test/mock-repository-content)
172
* Click on the "access params" button on the top right and change the base url to the location where you saved the sample folder (e.g. `file:///dnet/test/mock-repository-content`)
173 173
* Click on the meta-workflow "Collection and Transformation" and configure its workflows with the missing parameter for the transformation rule 
174
	* click on the yellow "parameters" button of the trasnformation workflow and select the rule <code>dc2dmf_DRIVER</code> 
174
  * click on the yellow "parameters" button of the trasnformation workflow and select the rule `dc2dmf_DRIVER`
175 175
* Ensure the launch mode is set to "Auto" for each workflow 
176 176
* Click on the Launch button of the first ("collect")
177 177
* Wait for all the workflows to complete: collect, transform, index, oai, and oaiPostFeed
178 178
* Verify that the records get transformed and indexed: click on MD Inspectors --> D-Net content checker and perform some queries
179 179
* Verify that the aggregated records are correctly exposed via the built-in OAI-PMH publisher at: 
180
	* http://${container.hostname}:${container.port}/${container.context}/mvc/oai/oai.do?verb=ListRecords&metadataPrefix=dmf for the DMF metadata format
181
	* http://${container.hostname}:${container.port}/${container.context}/mvc/oai/oai.do?verb=ListRecords&metadataPrefix=oai_dc for the OAI_DC metadata format
180
  * `http://${container.hostname}:${container.port}/${container.context}/mvc/oai/oai.do?verb=ListRecords&metadataPrefix=dmf` for the DMF metadata format
181
  * `http://${container.hostname}:${container.port}/${container.context}/mvc/oai/oai.do?verb=ListRecords&metadataPrefix=oai_dc` for the OAI_DC metadata format
182 182
	
183 183
#Need support?
184 184
Do not hesitate to contact dnet-team@isti.cnr.it

Also available in: Unified diff