Use case 3. Enriched data return scenario Cultural heritage institutions that have delivered content to Europeana, using a basic or advanced profile, want to re-ingest or reuse enriched data Europeana offers in return, to be incorporated in their own system again and for other services.4 The XXX should enable them to re-use, or get back enriched data from Europeana. Granular possibilities of integrating this data in their own system (not necessarily their CMS) should be offered. They should be able to use and/or reuse it wherever they want and for instance publish it on their own website. As mentioned in section 2 the reason for choosing to have one return scenario for both profiles is that currently both profiles need advanced options for customisation when receiving returned enriched data from Europeana. They need to be provided with maximum granularity and given all possible mechanisms to control the enriched data return. Whether they use these or not, is up to them. An institution with an advanced profile might choose for a basic execution of this return scenario with little customisation and more basic settings because they already closely monitored the quality of the supplied data and pre-calculated the kind of data enrichment they expect to get back from Europeana. Basic profile institutions might want to control and configure the return of enriched data more closely and use more advanced settings when returning data. In doing so, basic profile institutions learn more about their own data quality from the advanced return scenario. Therefore the possibility that they might upgrade to the advanced supply scenario the next time may increase. Use case 3: Enriched data return scenario: A content provider who has contributed data to Europeana (whether it has been contributed directly by the institution itself or via an aggregator) wants to receive and re- use enriched data from Europeana either inside or outside their own CMS, for instance in another local or web based system or on their website. Goal: Using the XXX to re-ingest enriched data from Europeana for the purpose of re-use by the content provider (whether that is by reintegrating selected enriched content into their own CMS or to collect and keep it somewhere outside their CMS, like their website). Actor(s): Content providers, including aggregators, who have contributed data to Europeana, independent of the fact if they contributed data within the basic or advanced supply scenario.
Use case 3. Intra-CMF In this scenario the experimenter uses the CMF’s own I&M software (e.g.: GEMINI5 on ProtoGENI) to configure and manage his measurements and, as such, I&M Portals will not be needed to configure intra-CMF measurements, only to visualize the results. In order to make the measurement results available to the Portals, I&M Architecture will install gateways within the slice whenever needed. These gateways should be able to: • Identify measurements being performed within the slice; • Register the measurement data on a Measurement Information (MI) Service, to be presented in Section 8.2, so external clients such as Portals can discover this data; • Provide an API for data retrieving, so external clients such as Portals can fetch the measurement data for visualization and backup; Figure 7-2 shows a scenario where a gateway is deployed inside an OCF slice. In this scenario, the steps for visualizing the measurement results are:
Use case 3. 2: Provide Access rights
Use case 3. 4.2: Search in single records This use case illustrates an end-‐user accessing a DIP with single records. If the DIP contains metadata on files / documents, the user can navigate a list and/or search. If there are no metadata (or they are embedded in the documents) the end-‐user can only search.
