Kickoff Meeting Agenda for Interoperable Geographic Project
•Download as PPT, PDF•
1 like•828 views
This document summarizes the agenda and key discussion points from a kickoff meeting for the Interoperable Geographic Information for Biosphere Study (IGIBS) project. The agenda included introductions and presentations on the project context from various stakeholders. Discussion focused on aligning objectives, prioritizing deliverables, and planning the project workflow, including stakeholder engagement, application development, and access control using Shibboleth authentication. The goal is to improve interoperability between public and academic sector geospatial data and services.
![Kickoff Meeting for the Interoperable Geographic Information for Biosphere Study (IGIBS) Project Welsh Institute for Sustainable Education, 11 th April, 2011, Chris Higgins, Project Manager, [email_address]](https://image.slidesharecdn.com/kickoff-meeting-for-the-ibis-project-110420041616-phpapp01/85/kickoff-meeting-for-the-interoperable-geographic-information-for-biosphere-study-igibs-project-1-320.jpg)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Kickoff Meeting Agenda for Interoperable Geographic Project
Similar to Kickoff Meeting Agenda for Interoperable Geographic Project (20)
More from EDINA, University of Edinburgh
More from EDINA, University of Edinburgh (20)
Recently uploaded
Recently uploaded (20)
Kickoff Meeting Agenda for Interoperable Geographic Project
- 1. Kickoff Meeting for the Interoperable Geographic Information for Biosphere Study (IGIBS) Project Welsh Institute for Sustainable Education, 11 th April, 2011, Chris Higgins, Project Manager, [email_address]
- 2. Agenda WP4: Access Control 1530-1600 WP3: Application Development 1500-1530 WP2: Stakeholder Engagement 1430-1500 WP1: Project Management – Project Plan 1400-1430 Lunch 1230-1400 IGIBS in the University Aberystwyth/IGES context 1155-1230 IGIBS in the Welsh Assembly Government context 1120-1155 IGIBS in the EDINA/JISC context 1045-1120 Intro to the Dyfi Biosphere 1030-1045 Scene setting 1015-1030 Participant Introductions 1000-1015
- 3. Align Business Objectives Institute of Geography and Earth Sciences EDINA Welsh Assembly Government Within limits of the JISC programme aims and the project proposal. Suggest we spend afternoon fleshing out project plan and maximising the size of the sweet spot in the middle
- 20. What EDINA GETS from the project depends on …
- 25. With your help today, consider how to re-write sections, re-package and post Core IGIBS team (CH, BC, MK) to meet as close to possible to weekly at IGES and blog regularly. All others welcome any time either physically or by Skype
- 47. Key Roles within an Access Management Federation SP SP SP SP SP SP SP SP SP SP SP Coordinating Centre Federation Service Providers Identity Providers Users Organisations SP SP IdP IdP IdP IdP IdP IdP
- 48. Example Shibboleth Login Procedures http:// www.switch.ch/aai/demo/medium.html
- 55. An INSPIRE Federation? OWS Providers Member State organisations, eg, INSPIRE Points of Contact WMS Key organisations, eg. EEA, JRC WMS WMS WMS WMS WMS WFS WFS WFS WFS WFS WFS Coordinating Centre IdP IdP IdP IdP IdP IdP
Editor's Notes
- Have met each partner organisation individually. First time (only time?) have all met. By the end of the day I would like: Some ideas Common understanding Agreement on key milestones in project plan Exactly what happens in the afternoon driven by the morning Maybe over lunch; each partner lists top 3 objectives they have for this project
- Exactly what happens in the afternoon driven by the morning, but go through Work Packages Have asked the partners to prepare: - essential background to this project from their perspective what others need to know to understand why in IGIBS. - what they wants/expects out the project (and what you want and what you get might be different) Over lunch; each partner lists top 3-5 objectives they have for this project
- International Definition of sustainable development Very broad Bilingual
- Do we seek endorsement of IGIBS?
- From: Annual Briefing - progress November 2009 - February 2011.DOC
- Mostly from: Annual Briefing - progress November 2009 - February 2011.DOC
- JISC supports higher and further education by providing strategic guidance, advice and opportunities to use Information and Communications Technology (ICT) to support research, teaching, learning and administration. The activities in this call are targeted at addressing particular aspects of the infrastructure but they all contribute to the rich vision of infrastructure for education and research. They contribute to the delivery of JISC’s strategic objectives with particular emphasis on the following objectives as set out in the JISC Strategy: To provide cost-effective and sustainable shared national services and resources To help institutions to improve the quality, impact and productivity of academic research
- Mention MIMAS
- Element of knowledge transfer about this project
- To what extent does this approach invalidate the need for producing written reports Lot of material online; including financial details
- To what extent does this approach invalidate the need for producing written reports Lot of material online; including financial details
- There are other ways of dividing this, eg, by discipline, training Need to be realistic: 7 months, 2 days a week
- Software Outputs It is expected that software outputs will normally be licensed as open-source unless a case is made to the contrary and accepted by the evaluation panel. Applicants should make clear the licence under which software outputs will be released, mechanisms that will be put in place for community contribution (users and developers) throughout the project, and the sustainability plan for the software beyond the period of project funding. Applicants should consult with JISC's open source software advisory service OSS Watch [1] and the Open Middleware Infrastructure Institute UK [2] on matters relating to open source software development. Applicants should refer to JISC's Policy on Open Source Software for JISC Projects and Services [3] . To be able to re-use the software it must be of a certain quality and maturity. For example, it must have supporting information, FAQ, installation guides, test data etc. to help others use it. In addition to the advice from the OSS Watch and OMII-UK, elements that contribute to software quality and project maturity are outlined in the Software Quality Assurance (QA) and Open Source Maturity Model (OSMM) Development guidelines. [4] Projects will be expected to follow the recommendations from these sources of guidance. [1] OSS Watch http://www.oss-watch.ac.uk/resources/bidsupport.xml and http://www.oss-watch.ac.uk/resources/adviceforprojectbids.xml [2] OMII-UK http:// www.omii.ac.uk / [3] Open Source Policy http:// www.jisc.ac.uk/fundingopportunities/opensourcepolicy.aspx [4] Software Quality Assurance (QA) and Open Source Maturity Model (OSMM) Development guidelines:
- I will need to understand under what format the input files are provided. Different libraries support different formats.
- Which of the above should be automatically probed, provided by the user or just ignored!
- Make this generic to show the components of a federation
- User attempts to access a Shibboleth-protected resource on the Service Provider (SP) site. User is redirected to the WAYF in order to select their home organisation (IdP). Part of same exchange as 2. IdP ensures that user is authenticated, by whatever means IdP deems appropriate After successful authentication, a one-time handle (a SAML artefact) is generated for this user session. SP uses the handle to request attribute information from the IdP for this user IdP allows or denies attribute information to be made available to this SP Based on the attribute information made available, SP makes authorisation decision, ie, allows or denies the user access to the resource.
- Not just SDI, many kinds of information infrastructure require access control Typically, authentication is a pre-requisite. Some use cases where you don’t, eg, public Barriers to interoperability include; cost, vendor lock-in, lack of a support community, not standards based, etc Return later to those last points