QVIZ

QVIZ, Query and context based visualization of time-spatial cultural dynamics

QVIZQuery and context based

visualization of time-spatial

cultural dynamics


Summary of QVIZ

Patrik Svensson

Fredrik Palm

Umeå University (UMU)


Outline of the presentation

• Summary of QVIZ general results

• Examples of innovation– QVIZ integrated software platform– Data models of integration– Reports and deliverables


Summary of QVIZGeneral objective:Enhance access to Archival/Cultural Heritage resources by subscribers such as students, researchers, local historians and professional archival users. Rather than answering full text multilingual queries, multilingualism will be addressed at the knowledge level. Linking querying and visualization in a community knowledge building process will motivate European citizens to form communities that enhance access to and usage of archives.

• QVIZ has delivered enhanced and contextualized access using visualization of time, space and community activities.

• QVIZ has involved two national archives using an integrated resource model based on ISDA(G) and the Administrative unit ontology.

• QVIZ has enabled wider usage of archival resources through the integration of a collaborative knowledge building process.

• The QVIZ approach has also created a need for sophisticated knowledge services within the archival sector.

• Improved access to European CulturealHeritage


QVIZ – a model for accessing European archives• Access to 75,646 archival volumes.• Between 16 and 18 million digital images.• 73,030 administrative units linked by 218,518

relationships.• The administrative ontology covers the whole

of Europe – provides access point to archives across Europe.

• Multilateral user to user collaboration.


Examples of innovations

• Visualization of archival resource context using names, relations, time and location of administrative units.

• The context of archival resources does not need to follow today’s borders.

• Integrating user activities and knowledge building processes.

• Dynamic and responsive user interfaces.• Unified resource model adopting ISDA(G) enables cross-

border access to administrative units (present and historical).

• ”Where and When” overcomes the initial barrier when searching and using archival resources.


QVIZ integrated platform


Integrating models of archival resources


Administrative units


User domain content model


QVIZ scientific and technical documentationD.2.1 State of the Art D.3.1 Specification of Access Methodologies for Selected User Scenarios D.3.2 Administrative Ontology (Schema) D.3.3 Ontology for Domain (Schema) D.3.4 Knowledge Content Model (KCO)

D.4.1.3 System Specification and Requirement Report D.5.2 Toolkit Architecture Report Version 2 D.6.4.2b Prototype 2b

D.7.3 Assessment Methodology and User Scenario Test Plan Final D.7.1.2 Software Validation Online Diary and Final Validation Report D.7.4 Evaluation Report of Case Study

D.8.1.2 Exploitation Plan TIP and IPR-plan final D.8.2 Dissemination Plan


Demo sessionLinda Lindgren



QVIZ symposiumPatrik Svensson



Formal part of the presentation

Patrik Svensson

Fredrik Palm



Outline of the presentation

• QVIZ consortium

• QVIZ collaboration, meetings and communication

• Review actions

• Efforts and financial information


QVIZ consortiumUoP• Research in administrative units ontology• Design and implementation of administrative

ontology• Leader of WP 3 – Knowledge and analysis

SNA• Expert in usage of archival and cultural heritage

content• Integrator of QVIZ-service in SNA’s content portals• Leader for WP2 & 8 – Requirements & Exploitation

and disseminationNAE• Pedagogical expert in archival and cultural heritage

content• Integrator of QVIZ –service in SNA’s content portals• Leader of WP 7 – ValidationUMU• Technical coordination across work packages• Development and integration of tools for dynamic

queries and social bookmarking.• Software validation• Dissemination and exploitation• Leader of WP 1 – Management

TID• Technical expertise in E-services

development and documentation• Business and license handling relevant to

exploitation plans• Leader of WP 4 – Technical specificationSRFG• Collaborative social software for knowledge

building• Ontology schema design• Leader of WP 5 – Core component

implementationREGIO• Development of time-spatial technological

components using administrative ontology and historical maps.

• Internet map servers and development of web mapping software

• Leader of WP 6 – Contextualisation and visualisation implementation



QVIZ collaboration

• Regular PMT-meetings for coordination of shared effort across work packages.

• Physical consortium meetings and workshops.

• Steering groups meetings.


A PMT-meeting (13/2/2008)• Acute issues • Review (Fredrik 5 min)

– The review have been set for the 16th to the 20th of June. This date has been decided upon by the project officer. All partners need to have one representative present. Cost can be brought up during the 45 days after the project has ended. Considering that this review takes place after these 45 days Fredrik will check what kind of cost that can be taken into account.

• WP 3 (Fredrik 5 min) – Fredrik reported in Humphrey’s stead that UoP has delivered the data structure on

administrative unit ontology and are now working on the Deliverable 3.2. • WP 5 & 6 (Bob 5 min)

– Bob: Mostly bug fixing and improvements to the ontology. And of course work on the user manual. The user manual is supposed to be finished by the 15th of February.

– Fredrik: Map and FB are mostly stable. Work will be performed on completing the Estonian administrative units. Mikael will be responsible for the Toolkit report and will receive assistance and back up from Laura. This report needs to obtain a high quality since it will be very important and have many uses.


PMT-meeting continued• WP 7 (Tõnis 5 min)

– Mostly functionality testing has been performed on the Map and Faceted Browser and bugs have been reported. The CET will have a new version today and the testing on this will be commenced. Linda is working on the D 7.1.2 and it will be finished shortly. Furthermore, preparations and test case drafts are being produced for the usability test. The code freeze will give the testers the opportunity to decide which version to test usability on.

• WP 8 (Fredrik and Johan 5 min) – Johan: Exploitation draft is being updated. Any feedback on the version that is found on the wiki must

be commented in writing and emailed to Peder and Johan by this Friday (February 15th)! Specifically Laura’s table need to be commented, it is found within the appendix. An update of this table will be put up under work in progress by Johan.

– The 19th of February; Partners own exploitation expectations must be specified and handed in to Peder and Johan; Requirements for the archives to be able to join must be updated (Paula and Mårten); List of Content Providers made by Tõnis; More input on contacts taken; All this information needs to be emailed to Peder and Johan by the 19th of February!!

– Fredrik: A meeting has taken place between Jill Cousin (EDL), Peder Andrén and Fredrik Palm. The outcome of that meeting was that QVIZ do have some potential for the European Archives and QVIZ will be invited to take part in a technical meeting round the 17th of March. Peder will handle the communication surrounding that meeting. Who will be invited from QVIZ will be reported later on.

• Other issues – Symposium dates have been fixed, more information will be posted on the wiki during the day and some

information can be found on the web. The commission has been informed of this symposium. All partners are to meet in Umeå some days before the symposium.

• Next meeting – 27th of February at 13.30 CET.


A QVIZ consortium meeting

22nd of January 2008 at REGIO• 9 .00 Welcome - Fredrik Palm• 9.10 Walkthrough of the program - Mona Bonta Bergman• 9.20 Exploitation including product definition - Peder Andrén• 12.30-14.00 Lunch• 15.00 Dissemination - Mona Bonta Bergman• 16.30 Presentation of Wednesdays workshops Tõnis Türna and

Fredrik Palm• 17.15-17.30 Short evaluation of the day- Fredrik Palm


A QVIZ-meeting continued23rd of January 2008• 9 .00 Workshop, Testing at NAE, Development at Regio. Tõnis Türna and Mikael

Berglund• 12.30-14.00 Lunch• 13.30-17.30 Continue workshop• 19.00 Dinner24th of January 2008 at REGIO• 9 .00 Introduction – Fredrik Palm• 9.10 Walkthrough of completed functions and feedback from testing activities-

Mikael Berglund and Tõnis Türna • 10.00 Presentation of discussion topics - Fredrik Palm• 10.15 Smaller discussion groups• 12.30-14.00 Lunch• 14.00 Gather to present discussion result- Fredrik Palm• 15.15-15.30 Evaluation of the consortium meeting – Fredrik Palm


Example of steering group meeting


Example of QVIZ Workshop

WS 2 Development, Mikael BerglundObjectives • Find the most important functionalities • Integrating points, 1) functionalities, 2) user interface • Improving the efficiency of the GUI • Common graphic profile Expected Results • Time plan for completely fixing the bugs for the most important

functionalities. Preparation • Evaluate ranking made in

D 4.1.3 System Specification and Requirement Report (pdf-file)


Review action #1

Integration:• Consortium partners created a single integrated scenario within

WP2 and WP4. The single integrated scenario outlined the QVIZ-package describing the most prioritized achievable result. This was communicated and agreed in July/August 2007.

• Single integrated scenarios and functionalities have been implemented for easy interaction with archival portals, and knowledge creation and searching.

• Some previous scenarios, and functionalities were given lower priority, such as the Mobile scenario which was not consistent with the overall scenario.

• The user manuals are public and include also a video tutorial for most relevant activities.


Review action #2

User involvement and validation:• The consortium defined the main target groups of QVIZ.

Research and development addressed the need of these groups. These target groups where used for the case-study and usability testing.

• Validation :– Functionality testing through explorative testing has been used to

validate software quality. 20 test charters have been designed and tested.

– Functionality testing have also given feedback about usability and information about compliance towards the specification in the D.4.1.3

– Dialogue with end user in various dissemination activities.


Review action #3

Exploitation and dissemination:• The draft of exploitation plan was delivered in November 2007• Business or governance models have been established. There are

plans up uptakes of somewhat modified parts of QVIZ by NAE, SNA, EUROPEANA and APE-net are discussing models of uptake of result, but only a tentative agreement has been made.

• Efforts have been made both to maintain a high level of dissemination and to document these more extensively in relevant documents. Most relevant presentations and papers, and all public deliverables are now available on the QVIZ website


Review action #4

Quality of reports and research result

• The reviewers requested the consortium to produce deliverables of more consistent quality.

• UMU hired one additional communication manager to focus on quality assurance of reports, and allocated additional resources to achieve deliverables of consistently high quality.


Recommendation: Page: Corrective action:Main recommendations:The consortium shall urgently share a concrete and realistic definition of the new product it intends to exploit at the end of the project. This should not be a loose collection of technologies but a tightly integrated system that will impact on the targeted domain

4 Consortium partners created a single integrated scenario within WP2 and WP4. This provided input and clarification of the main user workflow of QVIZ-platform. The output is evident in the D.4.1.3, D.3.3, and D.5.2, D6.4.2b, D.7.1.2 and D.7.4.

The consortium must define credible and real-life scenarios with the end-users that will be used to validate the system.

4 The consortium defined the main target groups of QVIZ. Research and development addressed the need of these groups. These target groups where used for the case study and usability testing.

The consortium should stick to the contractual Description of work and focus on integration activities instead of proposing new research activities.

4 Focus has been on the single integrated scenario. Prioritization has also implied that only the most critical functionality has been implemented.

The consortium is requested to deliver a draft version of the exploitation plan on month 15, including an analysis of the current competition (or future competition) and a first argumentation on the benefits of the proposed system against competition. It shall also identify content providers and possible business models.

4 Delivered in November 2007.

The consortium is requested to deliver a comprehensive user manual for each of the next software results, including the next integrated system

4 Done. The user manuals are public and include also a video tutorial for most relevant activities.

Recommendations:Product Definition: The consortium should define a realistic and focused product definition that is shared and adopted by all the participants. In particular, the targeted customers must be defined and their overall needs and constraints identified.

9 The single integrated scenario outlined the QVIZ package describing the most prioritized achievable result. This was communicated and agreed in July/August 2007. This integrated scenarios effected the prioritization made in D.4.1.3.

Some previous scenarios and functionalities were given lower priority, such as the Mobile scenario which was not consistent with the overall scenario.

A business or governance models have been established. There are plans up uptakes of somewhat modified parts of QVIZ by NAE, SNA. Europeana and APE-net are discussing models of uptake of result, but only a tentative agreement has been made.

End-User Implications & Validation: The consortium shall urgently implement a more user-centered methodology by:

Identifying end-users and potential customers

Involving them in the definition of real-life scenarios

Carrying out a professional and traceable validation that will be used to finalize the specifications of the final system.

9 Recruitment of validation and testing competency.

Dialogue with end users in various dissemination activities.

Major work has been done in terms of validation.

Functionality testing through explorative testing has been used to validate software quality. 20 test charters have been designed and tested.

Functionality testing has also given feedback about usability and information about compliance towards the specification in the D.4.1.3

Integrations: The reviewers strongly recommend the consortium to tightly integrate the results in one seamless framework while avoiding the dispersion of the results, which is not acceptable.

The reviewers recommend the delivery of user-manuals for each software module, including the integrated system.

9 Single integrated scenarios and functionalities have been implemented for easy interaction with archival portals, and knowledge creation and searching.

User manuals of good quality have been delivered. A video tutorial has been developed.

Exploitation planning: The consortium management should allocate resources to the preparation of the exploitation of the final system. For that purpose, the reviewers request the delivery of a draft of the exploitation plan on month 15 including the product definition, the targeted market (with user definition), an analysis of the competition (or future competition) and a first argumentation on the benefits of the proposed system (and technologies) against competition. Also identify content providers and possible models.

9 The draft of exploitation plan was delivered in November 2007

Dissemination: The presentation of the dissemination activities should be more detailed. Published material should be available on the website.

9 Efforts have been made both to maintain a high level of dissemination and to document these more extensively in relevant documents. Most relevant presentations and papers, and all public deliverables are now available on the QVIZ website.

Quality report: The reviewers request the consortium to produce deliverables of more consistent quality.

9 UMU hired one additional communication manager to focus on quality assurance of reports, and allocated additional resources to achieve deliverables of consistently high quality.


Person month effort year 2

Explanatory reason for difference• Mobilizing integrative work after M12 Review – more person

months were needed. • Umeå University intensified its effort in a major mobilization

during the second year – thus strengthening the coordinator’s role in the project to achieve a high level of integration.

• Personnel were recruited for technical coordination/integration, software validation, scientific quality assurance, dissemination, quality assurance of deliverables and exploitation.

• REGIO, UMU and UoP did more person months than planned, primarily due to the integration work with UMU and also because it was not possible to recruit as skilled persons as needed, therefore less senior persons needed more time.


Comments on costs (draft)

• QVIZ has used about 70 person months more than originally planned. We estimate that the cost will be as budgeted.

• Travel costs were a bit higher for some partners, especially UMU, due to many persons involved and the exploitation, dissemination and integrative activities.

• Given the complexity of this project the extra effort has been required to deliver the high quality work that the consortium has collaboratively delivered.


WP2 Requirements

WP leader: Peder Andrén (SNA)




Principal results WP2:

• Generally: The interpretation of project objectives to User Requirements, Business Requirements, Functional- and Non-functional Requirements

• From User Groups, User Scenarios, Mock-ups to Use Cases

• Business Requirements• Deliverables


Deliverables WP2:

• State of the Art D2.1

Submission date: 30/09/2006

• System Specification and Requirement Report D4.1.3

Submission date: 29/10/2007


WP2 development:First year: • General User Scenarios, User Groups and Use Cases• Mock-ups and Story Boards• First phase Functional Requirement• Business Analysis • State of the Art Report D2.1

Second year:• Specification, prioritization, concretization and elaboration of

Target User Groups, User Roles, Use Cases. Functional and Non-functional Requirements

• Feeding the final results into the project via the System Specification and Requirement Report D4.1.3


Description of results

Definition of requirements of QVIZ target groups:• Family history researchers – Search and cooperate• Students – Educational assignments, individual and in

groups• Educators – Prepare and conduct comparative studies• Professionals (Authorities) – Search of specific

information


Description of results


Description of resultsUse cases and functional requirements

This list gives an overview of the use cases and their respective requirements. No. Description Prio

QVIZ-UC5 Get QVIZ account

QVIZ-RQ5:1 Create a QVIZ account M

QVIZ-UC60a AU selection from Faceted Browser

QVIZ-RQ60a:1 Select administrative unit from faceted browser M

QVIZ-UC60b AU selection from map

QVIZ-RQ60b:1 Select an administrative unit from map M

QVIZ-UC61 Set temporal filter.

QVIZ-RQ61:1 Setting of temporal filter using timewindow M

QVIZ-UC62 Removal of the temporal filter using "Remove Time Filter" button


Description of resultsQVIZ-UC60a: AU selection from Faceted Browser

Ordinary sequence:

1. "Map" zooms onto the selected Administrative Unit. The Administrative Unit is drawn on the layer "SELECTED" highlighted with a red border.2. "Faceted Browser" highlights the selected Administrative Unit.3. "Result List" displays web links to archival resources connected to the selected Administrative Unit. "Directly related resources" are displayed first, "Indirectly related resources" second.4. "Result List" will for every archival resource display a web link to display social bookmarks for that particular archival resource.5. "CONTEXT" shows the following information: Administrative Unit name, Administrative Unit minimum creation date, Administrative Unit maximum abolition date,6. Chronological list of Administrative Unit polygons (with Administrative Unit name, Administrative Unit creation date, Administrative Unit abolition date).7. "TIME-WINDOW" does not change.8. "TIME-SLIDER" moves to the start (or end) of the Administrative Unit time period depending on the position of the "TIME-WINDOW". That is because the "TIME-SLIDER" has to fall into the period defined by "TIME-WINDOW".


Description of WP2 results:

The work in WP2 laid the foundation for the successful result of the project. Among the success factors were:

• The time taken for a knowledge building process within the Consortium

• The non-wavering focus on USER requirement – not on institutional requirements


Drawing on the result of:• The collected experience from SNA and NAE

on user needs• Existing surveys and questionnaires from

partner archives• Analyses of the extensive e-mail

communication between the service department of the partner archives

• Previous national projects




• The Requirements aimed the project result not only towards a set of recommendations, a prototype or a proof of concept, but for an actually working system



QVIZ an Integrated Distributed System• A strong requirement for a distributed system

Business Model• QVIZ handle paid content• A market analysis: Digital archives information – a

global business on the internet• From a DCM-Business model in WP2 to a Governance

model in WP8• Marketing a toolkit or marketing of an integrated

system – or both



WP3Knowledge and Analysis

WP Leader: Humphrey Southall

(UoP)




Principal results:• Selection of archival documents

– ISDA(G) resources from NAE and SNA totaling 75,646 volumes

• Development of data model for Administrative Unit Ontology– Pioneering hybrid ontology/GIS– 73,030 administrative units– 218,518 relationships between them– 75,986 boundary polygons

• Definition of domain ontology– Handling the user content and relations to archival resources

• Definition of Knowledge Content Object– Enabling export of content object in innovative facet

encapsulating


WP3 Deliverables:

• Administrative Ontology (Schema) version 3 (M23)

• Knowledge Content Model (M19)

• Domain Ontology Schema (M19)

• Specification of access methodologies for selected user scenarios (M10)


WP3 development:• Year 1: Defining knowledge content

– Identifying domain ontology– Defining AUO requirements– Constructing first prototype (Estonia only)

• Year 2: Building knowledge content– Assembling archival content– Fully specifying AUO schema– Constructing high-level AUO (Europe)– Integrating AUO data for Sweden, Estonia, UK– Finalizing the key usage scenario and Domain

ontology– Finalizing the KCO-report


Overview of domain model


Sources for QVIZ Administrative Unit Ontology

• Europe: New gazetteer constructed at UoP, partly from Hertslet The Map of Europe by Treaty 1814-1891

• England: F.A. Youngs, Guide to the Local Administrative Units of England (Royal Historical Society, 2 vols., 1981 and 1991)

• English Manors: TNA Manorial Documents Register

• Estonia: Name authorities and GIS files from NAE

• Scotland: Scottish Archives Network gazetteer of Scottish places (counties, parishes, burghs)

• Sweden: National Archival Database (NAD)

• Wales: M. Richards, Welsh Administrative and Territorial Units (Cardiff: University of Wales Press, 1969)


Part of the AUO Typology

Thanks to Vojtech Kupca (UMU) for these visualisations of the ontology


Unit relationships• All held in single

table, allowing many-to-many relationships

• Current system has 73,030 units but 218,518 relationships

• Have dates,authorities, etc

g_unit

http://www.icpsr.

umich.edu/DDI/

g_name

g_status

http://www.icpsr.

umich.edu/DDI/

g_rel_type

http://www.icpsr.

umich.edu/DDI/

g_rel http://www.icpsr.

umich.edu/DDI/

• IsPartOf• SucceededBy (‘see also’)• AdministeredBy• Boundary Changes

– ReducedToEnlarge– ReducedToCreate– AbolishedToEnlarge– AbolishedToCreate– BoundaryChange (other

unit unknown)


Modelling the history of Estonia


0

10000

20000

30000

40000

50000

60000

1 2 3 4 5 6 7 8

Numbers of units with different

numbers of names in QVIZ AUO


Count of number of names per languageLANGUAGE NUMBER OF NAMES

ENGLISH 62603

SWEDISH 7507

ESTONIAN 11973

GERMAN 5032

WELSH 1069

FRENCH 61

GREEK 3

ITALIAN 3

RUSSIAN 2

TURKISH 2

OTHER LANGUAGES WITH 1 NAME EACH 26


Numbers of polygons over time


Tartumaa, Estonia, View 1

NB all relationships between units are hyperlinks

Screenshot is of the validation interface developed at UoP


Tartumaa, View 2


Tartumaa,View 3

• AUO can hold multiple boundaries for a unit, for different dates– Holds multi-

polygons• Although

system holds 75,986 “footprints”, these cover only 37,772 of the 73,030 units

• Enables “history of point” listing

Remember – All three “views are into the one data structure


QVIZ AUO – E-R Diagram

g_unit

PK g_unit

g_hintFK1 g_unit_type g_centroid g_place g_duration im_auth im_note ul_auth ul_note created_by notes

g_name

PK g_seq

FK1 g_unit g_nameFK2 g_name_status g_language g_duration im_auth im_note ul_auth ul_note created_by notes

g_status

PK g_seq

FK1 g_unit g_status g_duration im_auth im_note ul_auth ul_note created_by notes

g_rel

PK g_seq

FK1 g_unit g_rel_toFK2 g_rel_type g_part g_part_area g_part_area_measure c_date_1 c_pop_1 c_hous_1 c_date_2 c_pop_2 c_hous_2 g_duration im_auth im_note ul_auth ul_note created_by notesFK3 g_unit_type

g_foot

PK g_seq

FK1 g_unit g_foot g_duration im_auth im_note ul_auth ul_note use_for_search use_for_stat_map use_for_bound_map

g_place

PK g_place

g_seed g_name g_container g_centroid created_by

g_authority

PK g_authority

FK1 g_auth_type g_auth_title g_auth_creator g_auth_creator_forename g_auth_publisher g_auth_pub_place g_auth_date g_auth_identifier url_works g_auth_rights g_auth_rights_string g_auth_description notes

g_auth_type

PK g_auth_type

notes

g_auth_type_level

PK,FK1 g_auth_typePK,FK2 g_language

g_label

g_unit_type

PK g_unit_type

FK1 g_type_levelFK2 g_jurisdiction g_type_period g_duration g_foot stat_only n_language n_label n_label_plural n_description n_full_description n_label n_label_plural n_description n_full_description n_short_label g_label g_label_plural g_description g_full_description g_short_label notes created_byFK3 g_type_function

g_type_level

PK g_type_level

g_adl_ft

g_type_level_label

PK,FK1 g_type_level

FK2 g_language g_label g_description g_full_description

g_name_status

PK g_name_status

im_auth sort_order

g_name_status_label

PK,FK1 g_name_status

FK2 g_language g_label

g_language

PK g_language

g_labelFK1 g_authority g_language_iso notesFK2 g_jurisdiction

g_status_type

PK g_status

FK1 g_unit_type n_language n_label n_short_label n_description n_full_description g_label g_short_label g_description g_full_description notes created_by

g_rel_type

PK g_rel_type

notes created_by

g_rel_type_label

PK,FK1 g_rel_typePK,FK2 g_language

g_label rev_label created_by

g_legal_rel

PK,FK1 g_unit_type

g_rel_type g_rel_unit_type notes created_by

g_jurisdiction

PK g_jurisdiction

g_label preferred_language email_address notes postal_address telephone_number

g_type_function

PK g_type_function

notes

g_type_function_label

PK,FK1 g_type_function

FK2 g_language g_label g_description g_full_description


QVIZ AUO Structure• Hand-drawn

version easier to follow– But NB slightly

out of date, e.g. no “jurisdictions”

• Blue tables are big and hold data

• Grey tables hold metadata


Background mapping of Europe• GSGS mapping based on British aerial

survey of Europe in early 1940s• 1:500,000 scale, with 1:4m overview• Full set of GSGS maps now scanned

with assistance from many libraries– No mapping of N. Sweden

• All re-projected toLambert ConicConformal

• Work is part ofWP6, but closelylinked to AUO

• Taken together,largest multi-national historicalGIS ever built– US NHGIS bigger

but less advanced

Index map to GSGS4072 and sample map of Berlin


Extensibility and sustainability• AUO systematically designed to be extensible

to cover all Europe in detail– Architecture does scale, unlike conventional GIS– Scanned map sub-system could cover larger scales

and range of dates

• AUO editing system has been developed to allow detailed updating via web site– Programmed using JSP to access Postgres

• Format based on ADL GCS defined allowing bulk ingest of additional states– Actually programming bulk ingest system beyond

scope of QVIZ



WP4 Technical Specification

WP Leader: Laura Albornos

(TID)




WP4 Principal results

Results: • The system architecture and data structures have

been developed in more grade of detail. • The framework for visualizing and querying

archival resources by a time-space interface based on maps and emergent knowledge structures.

• The integration of social software in order to utilize knowledge in research communities (in cooperation with other WPs).


WP4 Deliverables

• D4.1.3. System specification and requirements report,delivered in M16, contains the requirement specification made in relation to technological, collaborative and business models which form the basis for future specifications and implementations.

The tasks defined are user scenarios, use cases, storage requirements, non-functional requirements and functional requirements. Business requirements were included.

The technical specification included design for the system components, the functionalities of these components and their interaction, as well as defined high level system architecture. These aspects are based on the results gather from requirement and technical specification tasks in first phase.

• D4.1.2 System specification and requirements report that has been delivered in M9 and revised and modified for M12 producing a second version. This deliverable contains user scenarios, user cases, functional requirements and technical section.


WP4 Development• Increased level of detail with better associations between

component and data model and about data model used in each service.

• A more detailed ranking of components in layers and class diagrams specifications was provided, getting closer to specifying what we actually do.

• Interactions between components have been extended with sequence diagrams, APIs details and function schemas for resources, achieving critical definition of architecture diagram .

• Simplification increased clearity and made communication

• Knowledge services and functionalities.

• Detailed licensing and rights management about publication of practice communities.


Description of result

Environments Domains Operational objective WP

1. Query-Visualization and QVIZ Portal Environment.

QVIZ domain •To create innovative query/visualization capabilities •To design an ontology of European Administrative Units defining temporal and spatial relationships and to support dynamic map-based visualization.

WP3, WP5, WP6

2. Collaborative environment.

COP-domain and QVIZ-domain.

•To create innovative query/visualization capabilities•To create contextualization and knowledge building software for use by Communities of Practice (CoP)

WP5, WP6

3. Archive Portal Environment

Archival Domain &

Knowledge domain

•To apply state-of-the-art knowledge management technologies to the QVIZ archival

WP3, WP5, WP6

4. QVIZ Service environment

QVIZ and CoP domain

•To create innovative query/visualization capabilities WP5-T5.4

WP6

QVIZ architecture has been divided in environments based on domains from requirements specification and in which objective we want to carry out.Domains: User requirements analysis grouping user activities according to their working areas (requirement areas of work)Environments: It is a conceptual idea to group a set of system components that are performing actions to get the same operational objective. (Technical areas of work).


General overview of high level architecture



Architecture of the Query-Visualization Environment

Archival Resource Link Lookup and BookmarkStorage

Interface Specification among components:



Map and Query based exploration of archival resources

Map and Query exploration• Facets selection handle administrative units and community activity

• Facets can be ordered arbitrary to arrange your search of archival resources

• The Result List showing a list of archival resources.

• Explore time-spatial context. Discovery of resources:

•Time filter

•Visualizes the distribution of archival resources over time.



Social knowledge building and collaboration:

Descritiption and annotation to the bookmarks.

Communities can enhance resource description using knowledge ontologies.

Social bookmark organized in different collections

Create articles and publications.

Basis for re-use.

Social bookmarking of resources : Storage of reference to a resource. The social bookmark collected the resource context.



Definition of requirements of QVIZ target groups (from WP2):• Family history researchers – Search and cooperate• Students – Educational assignments, individual and in groups• Educators – Prepare and conduct comparative studies• Professionals (Authorities) – Search of specific informationRequirements and models• Provide an index of archival references connecting to administrative

unit (time and space)• Provide initial knowledge of relevant administrative ontology content• Provide services for social bookmarking of archival resources (such as

resource information services and redirect services.• Integrated QVIZ social bookmarking toolkit within their webportal• Provide synchronizing of provided content into QVIZ-system


WP4 Conclusions:

• Associations, traceability matrix, better specification were provided in second phase of the project, as result for the iterative process in which good results of first phase provide solid basis.

• Main job of this WP is establish the division of responsabilities and connections among the different technologies that are gathered together in this system.

• Goals for this iteration have been achieved with this approach, which have directly influenced in implementation WPs and validation and Exploitation.



QVIZ Architecture

Mikael Berglund

(UMU)


Architecture

• The software architecture discipline is centered on the idea of reducing complexity through abstraction and separation of concerns.


Separation of concerns

• Input from WP2

UMU

REGIO

UoPSNA

NAE

SRFG

TID

Software cooperation


Overview


Implemented components

Query Visualization

Faceted Browser Map Component Time-Bar

Map Server

RasterMaps

User Management

Users

Archive Resource Hub

Services

Collaborative Environment

Collaborative Environment RDF Store

Archive Portal

Bookmarking Client

QUIS Database

Ontology &Resources


Abstraction

• Well-defined interfaces between components• Components

– Archive Resource Hub

– User Management

– Collaborative Environment

– Faceted Browser

– Map Component

– Time-bar


WP5 Core Components

WP leader: Robert Mulrenin

(SRFG)




Principal results:

– Core tools and infrastructure for• Visualization of time-spatial dynamics – administrative

history • Enabling contextualized access of archival resources using

time-spatial dynamics and community properties• Dynamic queries and GIS support• Knowledge tools for supporting the use of models such as

administrative ontology and domain ontology• Social knowledge building tools for ontologies and social

knowledge content• Connecting content from archive to community knowledge

building

– Documentation of tools


Deliverables:

• D5.2 Toolkit Report– includes focus for the participation of new

Archives – requirements, tools, models– supplemented by Prototype User manual

• D5.1 Toolkit Report– First version


WP development:• Driving forces:

– 1st review feedback that formed WP4 specification and prioritization of use cases– Focus on achievable result – Dynamic and responsive interfaces– Integration across components and concepts (see WP6 also)– Validation and usability in WP7 (Validation) meant tight collaboration with technical work

• WP5 was the basic components for Integration – Archive resource modelling and specification– Further modelling, specification of domain models ( incl., extend T3.3,etc)– Specification of archive resource hub (ARH) and archive tools– Central authentication and Web 2.0 to support component integration

• Shared work between partners (plus WP7 driving force)– Archive hub specification and implementation– Social bookmarking and collaborative use of social bookmark of archival resources– Query Visualization & Time spatial components


WP results:D5.2 Toolkit and Integration (1/3)

• Query Vizualization Environment– Time spatial client and middleware– Faceted Query component (using QUIS model)– MapCat design, map and time-bar component

• Middleware– Central authentication over components / user management – Archive Resource Hub and archive basic client

• Editing system for master ontology for Administrative Units

• Tools to index archival resources


WP results: D5.2 Toolkit and Integration (2/3)

• Archive resource model and archive social bookmarking client enables integration of Query Vizualization environment and collaboration (CET).

• Archive resource description is critical object for sharing and handling social bookmarks of archival resources.

• Collaborative environement and knowledge tools for handling content, relations, communities and also typed content.

• Simple knowledge organisation (SKOS) building via tagging • Separate SKOS builder and symbol indexing of digitized

archival content.• KCO export tools (knowledge content objects) Knowledge

content, archive resources, CoPs.


WP results: D5.2 Toolkit and Integration (3/3)• Models, Data indexing tools

– Data models (T3.3 & WP5)– Data import software for archival resources and

specialized data-storage for facetted browser (QUIS)

– Archive integration tools for new archives – External integration via KCO

• Additional added value services for archival & user content

• Enhance access by exporting knowledge content


Contributions toward the objective: Enhance Access to Archival Resources

• Query Visualisation and Time spatial dynamics• Time spatial: historical GIS and facetted browser over admin

units, indexed archive resources, CoPs, Users

• Access Strategies• Archive Resource Hub and social bookmarking for integration

with archival portals• Tools to support archival institution to build index of archival

resources with the use of admin units.• Editing system for building administrative unit ontology• Export Knowledge content out to new environments

• Social knowledge tools• interrelate archival resources in new contexts (semantic network)

via the community to improve access to archival resources


Preparations for Exploitation

• Software Development branches – Development is active and continues during future

exploitation– Alternative branches (stable, development…) are being

released– Continue to gather interest and further feedback– Partners share common interest for archives and providing

services• Live Server(s) for QVIZ prototypes

– Can be upgraded with new features and refactored components.

– Some version will be kept stable.– Demo prototypes will keep attracting stakeholders and users



WP6 Contextualization and

visualization implementation

WP leader: Kalev Koppel

(REGIO)




WP6 Principal resultsObjectives Task results towards objectives (status)

Portal implementation and integration of tools

Several prototypes were published for the interactive user trials and demonstration purposes. Two national archival portals integrated social book marking toolkits and services.

Implementation of social software components

Web 2.0 user interfaces and visulization tools support integration with the query/vizualisation environment and archive social bookmarking resource visualization.

Design visual interfaces for concept- and time-spatial retrieval of CH-resources.

All required visual interfaces completed and integrated with relevant tools.

Create dynamic visualization of user queries connected to time-spatial administrative ontology

Facetted browsing in combination of dynamic thematic mapping and bar-chart visualization of statistical data (time-bar) implemented.


WP6 Deliverables• D6.4.1 Prototype 1

– Demo page of the time-spatial client: http://polaris.regio.ee/qviz/ – Demo page of the collaborative environment: http://

qviz.salzburgresearch.at/qviz/ • D6.4.2a Prototype 2a

– Time-spatial prototype 2a: http://polaris.regio.ee/qviz_p2a– CET prototype: http://qviz.salzburgresearch.at/qviz/ – Included D.6.1 and D.6.2.– With user manual

• D6.4.2b Prototype 2b– Time-spatial prototype 2b: http://polaris.regio.ee/qviz_test– Time-spatial prototype development version: http://

polaris.regio.ee/dev_test– CET prototype: http://qviz-dev.salzburgresearch.at/qviz/– With user manual and video tutorials


Development• Start in M12 and 1st first prototype published.• Scope narrowed and focus set on integration after the

project review in May 2007.• Several iterations of analysis, testing and coding carried

through in M12-24.• Prioritization of features• Publication of the prototypes p2a and p2b• Parallel integration of Collaborative environment and

Time-Spatial interface• Intention to go on developing software result beyond the

scope of the project.


Description of results – global view


Description of results - QVE• Facetted browser innovation• Map component and visualization• Time-bar component and visualization• History of the point tool and derived polygons• Server-side optimization

– Optimized queries for panning the map or changing time

– Vector data generalization


Description of results - CET• User management and UI integration among QVIZ

components

• Creating new content related to archival resources

• Relating resources to other resources

• Search and resource discovery

• Visualization and handling of knowledge content

• Visualizing primary resources– Archival social bookmarks

– Archival resource description


WP6 CONCLUSION• Most of the work done in the 2nd year

• Close interaction with component implementation (WP5) and testing activities (WP7)

• Objectives achieved

• Some functional highlights:• Facetted swapping

• Time-bar visualization

• Dynamic thematic mapping of resources

• Optimization of queries



WP7 Validation

WP leader: Tõnis Türna

(NAE)




Principal results

• Software validation was performed from November 2007 to February 2008 by representatives from the target groups

• Use Case/Scenario study was performed at the end of the project in Estonia and Sweden with an extended group of users

• The product was validated on the basis of the requirements and the user scenarios from WP2

• Test cases were derived from the requirements defined in WP2.• Functionality testing and usability testing was performed

simultaneously


Deliverables

• D.7.1.1 “Software validation diary and report version 1” (M12)

• D.7.3 “Assessment methodology and Final User Scenario Test plan” (M19)

• D.7.1.2 “Software validation diary and final validation report” (M24)

• D.7.4 “Evaluation report of Case Study” (M24)


WP development• Defining the scope, principles and techniques of validation (first year)• User involvement

– The results form WP2 were used in the first user trial (M12)– Selection of members in the test organization– Preparation of test cases based on specifications made in WP2 &WP4 (M18-

M20)– Professionally executing test cases, reporting bugs, validating requirements

and suggesting improvements (M18-M24)• Progress towards usable integrated system (M13-M24)

– Exploratory system testing in close cooperation with development team– Iterative process with quick and dynamic interaction between test

organization and development team– Regular meetings on suggested feature improvements– Coordination and collaborative time planning with development team– Continuous on-line documentation and test results


Result of functionality and usability testing• Validated software • Testing Notes • On-line Bug Reports and Feature Requests • User suggested improvements • System meets most of the requirements• Participants;

– Historians– Educators– Archivists– Software testers– Geographers– Journalists


Case study/scenario testing

Methodology– Focus on use of the features of the integrated platform – Functions were tested in the logical sequence following

scenarios– Similar research strategies, different data and regions– Same actions, comparable results

Additional participants;– Local historians– Educators– Genealogists– Professionals


Result of Case study

– Many unique features useful for target groups.

– Wiki technology was unknown and users desired a simplified and more intuitive GUI.

– Target groups felt eager to use and explore the system.



WP8 Dissemination and

Exploitation

WP leader: Peder Andrén (SNA)




Principal results:First year:• Market analysis • Communication of the QVIZ approach• First iteration of Exploitation and dissemination plan

Second year:• Elaborated exploitation plan with market study, actors and competitors of

the market, partner’s internal exploitation plans, content provider requirements, development road map

• Dissemination (all through the project) – conferences, workshops, the QVIZ symposium, printed documents, leaflets,

web sites, multimedia items, and posters • Business approach

– From a traditional commercial model towards more of a governance model


Deliverables:

• Draft of Exploitation plan

Submission in November 2007

• Exploitation Plan D8.1

submission date: 11/04/2008

• Dissemination plan D8.2

submission date: 31/07/2006


WP development:

• Focused efforts towards content providers in the European archival sector

• Produced a concrete requirement list for content providers

• Published an example of how to semi automatically generate Administrative Unit Ontology

• Focused dissemination and exploitation efforts on other European portal initiatives e.g. EUROPEANA and EPA/APEnet


Road map for using the results (1/5)

Exploitable results:

• The integrated QVIZ platform

Uptake and use of the result:

• Applies to European level initiative such as the i2010.

• Contacts and discussion about collaboration made with initiatives and project such as EDL, EUROPEANA, APE/EPA-net.



Exploitable results:• Dynamic user interfaces for discovery of archival resources

Uptake and use of the results:• NAE and UMU will cooperate using the facetted browser technology• SNA plans to use result from QVIZ in new archival portals of Sweden.• REGIO will use the improved products in their business.• To improve the product and services of Telefonica with application of digital

content management project.• UMU, SNA, UoP, for example through the Demographic Data Base department

and the proposed project Historisk befolkningsstatistik på internet (Historical population statistics on the internet).

• UMU plans to use result for time-spatial browsing in ”the strategic environmental database (SEAD)”



Exploitable results:Social bookmarking of archival resources within archival portals• Environment for social knowledge building based on archival resources• Domain ontology

Uptake and use of result• SRFG will use the QVIZ results in future FP7-projects.• SRFG will use software and models to be used by archives.• Interest by EUROPEANA initiative due to the need of addressing the

community aspect.• Interest by EUROPEANA initiative due to involvement of archival

content.• REGIO interest in the community based map-application.



Exploitable results:• European administrative ontology

Uptake and use of the results:• Has European coverage and can be used beyond the archival

domain such as demographic statistics and local history web-sites.• UoP are continuing to develop the AU Ontology editing interface,

and this will also be used by NAE and UoP will be using the Postgres-based version of the AUO as the foundation for their own new web site, replacing an Oracle-based infrastructure.

• QVIZ administrative ontology system will be covered by UK data archiving arrangements and so remain available for future projects covering more of Europe.

• UoP and UMU, SNA, REGIO intend to collaborate in future projects together



Exploitatable result:• Time-spatial indexes of archival resources

Uptake and use of results• SNA will continue to build index as part of ordinary work. • SNA will use result of QVIZ in future portals of SNA.• NAE will improve Semi automatic matching software to assist

building indexes.


How to join QVIZ as content provider?

• QVIZ can be used by content providers that are digitalizing archival document and providing internet portals for access

• They need to provide an index of archival references connected to administrative unit

• They need to provide initial knowledge of relevant administrative ontology content

• They need to provide services for social bookmarking of archival resources.

• They need to accept an integration of the QVIZ social bookmarking toolkit within their web portal.

• They need to provide synchronizing of provided content into QVIZ-system.


Business and goverance model

• The most feasible business model for the integrated QVIZ platform is to have the content providers pay for their archives to be accessible through QVIZ.

• The content providers make up the target group that has the most added value from the system by making the content of their archives more easily accessible to the public.


Dissemination:

• 32 conference and workshop presentations

• 8 publications

• 13 presentations for partners and future collaborations

• Numerous other presentations



Summary of QVIZ

Patrik Svensson


Date post:	09-Jan-2016
Category:	Documents
Upload:	cathy
View:	28 times
Download:	2 times