Structure of the Deliverable Sample Clauses

Structure of the Deliverable. ‌ The rest of this deliverable is structured as described in the following. In Section 2, we discuss the foundations of the PoF Reference Model, covering the characteristics of the model as well as the requirements, which did influence its development. In Sec- tion 3, we present the PoF Reference Model for an integrated information and preser- vation management system, which considers this combination as a joint ecosystem. In more detail, we describe a functional model and an information model. In Section 4, we relate the PoF Reference Model to the reference architecture of the PoF Framework. This architecture, which is based on the system architecture presented in deliverables D8.1 [ForgetIT(2014b)] and D8.3[ForgetIT(2014c)], maps the joint ecosystem of building blocks from the reference model on an architecture with three main parts: the Active Sys- tem, the Digital Preservation System (DPS) and the PoF Middleware. In the second part of the deliverable, we relate the PoF Reference Model to existing models and approaches, in order to ease adoption. This includes a discussion of the extensions required in an information system for becoming part of an information and preservation management ecosystem (Section 5) and a discussion on how to map the relevant parts of the model on an OAIS based DPS as well as suggested extensions to such a system (Section 6). We conclude the deliverable with a summary of the main insights, with ideas for future work and an assessment of the results compared to success indicators reported in the project proposal.
AutoNDA by SimpleDocs
Structure of the Deliverable. This deliverable consists of the following sections: • Introduction • Actions completed to date • Project progress • Content • Effective project management • Changes to the project scope or the risk register • Forthcoming actions
Structure of the Deliverable. This deliverable is divided into: • Content preparation: tasks performed in preparation of the ingestion plan (content providers meetings and ingestion forms) and in preparation of content ingestion (aggregator). • Ingestion plan: schedule that describes the status and the availability of the collections to be ingested by each content provider starting from the table in the DoW. • Monitoring ingestion process: the ingestion plan will be updated with the information provided monthly by the content partners in the content monitoring forms.
Structure of the Deliverable. The first section will outline the template used to describe the use case scenarios. It will also give some background to the use case scenarios by describing the user profiles they are based on and by motivating the choice of these profiles and use case scenarios in relation to the findings of the previous deliverable and the project’s Description of Work (DoW).
Structure of the Deliverable. The deliverable is structured in 9 sections: The present Section 1, as introduction to the document, presents the scope of the work carried out, the adopted methodology and the position of the deliverable in the Work Breakdown Structure of the project.
Structure of the Deliverable. This deliverable describes the final version of the TULIPP Reference Platform (TRP), and consists of four parts: •
Structure of the Deliverable. The rest of this report is structured as follows: section 2 describes the methodology of the roadmapping effort. Section 3 presents the analysis of the projects in connection with the exploration of disruptive technologies as previously identified in WP1 (Task 1.1). For each technology at first a short introduction is provided (subsection 1), the relevant projects on the European level are described and systematized (subsection 2). The research and the training needs from the projects are extracted and described. In section 4, thirteen possible future scenarios depict potential usages of disruptive technologies in different areas of digital government. Section 4.2 details the research and training needs collected with the help of the scenario analysis. Section 5 contains research and training roadmaps, where specific actions are described in detail. Section 6 outlines recommendations for the implementations of the roadmap actions for different stakeholders. Finally, section 7 concludes the report by briefly summarising the findings and explaining how the findings of this work package can be used in the subsequent work packages of Gov 3.0 project.
AutoNDA by SimpleDocs
Structure of the Deliverable. ‌ This deliverable consists of four main parts: condensing the ComfDemo message (1), dissemination (2), communication (3) and exploitation (4).
Structure of the Deliverable. The Deliverable D3.3 contains two different formattings of the Authority List of Art Nouveau creators:
Structure of the Deliverable. The deliverable includes spreadsheet documentation for each of the messages, XSD XML schemas for each pair (request/response) of messages and HMTL documentation/visualisation of the message structures. The XSD and HTML elements can be found in the zipped file attached to this Deliverable 3.4.1., whose contents are as follows: ✓ ARROW Reference Schema v0.1; ✓ Seven individual schema files for message pairs M1 – M7; ✓ One schema file for all code lists (enumerated types); ✓ One schema file containing structures common to all message pairs; ✓ One schema file containing structures not common to all message pairs, but common to message pairs M2 and M4 in the The European Library domain; ✓ Eight HTML files containing schema documentation for each of the above eight schemas; ✓ Various HTML and CSS files supporting display of the documentation; ✓ An ‘img’ folder containing the image file diagrams for the documentation
Time is Money Join Law Insider Premium to draft better contracts faster.