1 donors applications an overview. 2 introduction available donors applications –canada...
TRANSCRIPT
1
Donors applications
An Overview
2
Introduction
• Available donors applications– Canada– Switzerland– USA
3
CREATING NATIONAL NODES OF THE BIOSAFETY CLEARING-HOUSE
CANADIAN PROPOSAL
4
CURRENT SITUATION
• many countries would like a national node of BCH
• have IT/IM capacity to securely host applications
• do not have resources or time to develop applications
5
POTENTIAL SOLUTION
• CNBCH developed with scalability, reuse and capacity development in mind
• applications developed for CNBCH as base
• incremental work to make it portable
• development of stand-alone, open-source and platform independent suite of applications
• proposal made to UNEP in May 2004
***Proposal for nBCH
6
NATIONAL NODE FEATURES
• National subset of the BCH data– single window for a country’s records on the Central Portal
• Additional national context– information not possible through central portal
• Interoperable with Central Portal– compatibility of records– same overall look and feel– same general approach to functions
• Accommodate domestic requirements– ownership of records– multiple languages– specific graphics, links, disclaimers, etc.
7
COMPONENTS
• Metadata entry tool
• Relational database
• Search engine
• Web services
• Web site
• Web site management tool
8
TECHNICAL APPROACH
• Supports multiple languages.
• Default configuration is English.
• Platform independent, open-source.
• Developed using Java, XML, XSLT, SOAP.
9
CONTENT MANAGEMENT
• Static content created through a Web page.• Common formats currently supported:
– Decisions under 11.1– Competent National Authority– Laws and Regulations– Regional and International Agreement– National Focal Point– Other Decisions– Bibliographic Information– Organizations (Relevant Web sites)
10
CONTENT MANAGEMENT
• Records published to Web site with Web service.
• Can be used with any entry tool (Canadian, Management Centre, US or Swiss).
• Web service supports add, update & delete functions.
• Documents digitally signed.
11
FEATURES
• Customizable look and feel:– resolution– images– cascading stylesheet
• Customizable header and sidebar.
• Footer information extracted from XML document.
12
REQUIREMENTS
• Good knowledge of OO programming, XML and databases (if you wish to customize)
• Fairly recent server (at least P3 with 256MB of RAM)
• IT infrastructure (firewall, anti-virus, backup system)
• JDK 1.4.2, AXIS 1.1, Tomcat 5.0 (Server)
• JDK 1.4.2 (client)
13
INSTALLATION
• Procedure TBD for stand-alone
• Will be as simple as possible for the client (download executable)
• Currently have to install JDK 1.4.2 on client, then deploy application
• Will need to install required software on server
14
DOCUMENTATION
• Modeling– Component and deployment diagrams– Conceptual and Relational Model, Data Dictionary,
Integrity Rules Document– Use Cases, Use Case Realization, Activity Diagram,
Class Diagrams• User and Implementation documentation
– User Guide, Software Design Document, Installation Manual, Deployment Plan
• XChainJ available online:– http://xchainj.com/XchainJ_2.x_Training/CourseNotes.zi
p
15
WHAT is offered by Canada
• Provide upgrades packages for server application– Client application update will be deployed seamlessly to
clients from server
• XChainJ license includes 10 queries, up to 5 hours support
• Provide support to Regional BCH Consultants• Design and implementation questions (phone,
email, fax,…)
16
WHAT is not included
• Assumption that you have in-house expertise
• Configure servers, firewalls, back-ups, operating systems
• Will not do customization (contractor available at 50% of regular rate)
17
CREACIÓN DE NODOS NACIONALES DEL CIISB/BCH
PROPUESTA CANADIENSE 2
Aplicación Simple
18
Propuesta Canadiense Sencilla
• Existe otra propuesta de Canada más sencilla• Utiliza como aplicación de entrada de datos
directamene el Centro de Gestión del Portal Central
• Se instala en un servidor local (nacional) una aplicación Java
• Mediante webservices esta aplicación toma del Portal Central los registros del país y los hace disponibles en el website nacional
19
Aplicación canadiense sencilla
• Características– Configurable fácilmente– Multilenguaje– Permite vincularse con otras aplicaciones o portales ya
existentes
• Requerimientos-Servidor nacional, actualmente probado sobre Windows- Servidor de aplicaciones Apache / Tomcat - Software para webservices Axis
20
Aplicación canadiense sencilla
• Ventajas:– Simple de instalar y fácil de poner en operación– No requiere de una base de datos local ya que
la información se toma del Portal Central– Un único punto de entrada de información– El entrenamiento sobre el uso del Portal Central
ya abarca todo lo necesario– Bajo costo y requerimientos de recursos
humanos
21
The Swiss Biosafety Clearing-House(CH-BCH)
http://www.ch-bch.ch
22
Swiss policy concerning the CH-BCH
• Swiss political organization (Fed. State)– Decentralized functions and responsibilities
between Cantons, Federal Agencies and Offices
• Specific needs for Switzerland• User and group management• Workflow / Access right• Multilingual support• Flexibility• Interoperability• => Object-relational database management system
23
Swiss policy concerning the CH-BCH
• 4 options– Register data in the central portal using the Management
centre– Register data locally using database templates and send
data to the central portal– Make data available through a local website and allows
the central portal to crawl to retrieve metadata– Store data on national databases, and actively make
those data available through the central portal using BCH interoperability protocols
24
Swiss policy concerning the CH-BCH
• Choice of option 4: Interoperability– Major reasons:
• Swiss political organization (Federal State):• Need of a decentralized user and group management system• Data are physically stored in Switzerland• Security of the records• Mandatory Swiss specific information can be included in new
elements independent from the central BCH portal– Swiss biosafety information
– Public awareness
25
The CH-BCH development history
• Swiss environmental data catalogue: envirocat– 150 groups involved– Environment relevant data, projects, documents, Internet
links and resources– www.envirocat.ch
• Swiss Clearing-House Mechanism (CH-CHM)– Information platform related to biodiversity (CBD)– www.ch-chm.ch
– => Developed using IRMI:– Information and Resource Management Interface
26
System architecture
• IRMI:– Based and developed using open source products only
• Basic software for the application– Linux operating system– PostgreSQL Database program– ZOPE Content Management System (Python)
• Installation and hosting of the system• Redhat and SUSE Linux Distributions• Hosting at one central server (Apache)
• Open source components (free or very low cost)
27
System architecture: Client/server system
PostgreSQLdatabase
ZOPEmiddleware
Internet browserClient
Database adapter
Layout level
SQL SQL SQL SQL SQL
Module Module Module
Internet
Database -> Data
Bowser -> Communication
Middleware -> Application
Clie
nt
/
S
erve
rMozilla, Firefox, Netscape,Opera, Internet-Explorer
28
Description of the Swiss Biosafety Clearing-House application
• Description of the CH-BCH system– General concept– Utilization of elements– Elements attributes– Live demonstration– Conclusion / discussion
29
Description of the CH-BCH application
• General concept– Multi-user system
• Decentralized user and group management– Data input controlled by:
• Elements with specific attributes• Relationship between different element types• Interaction of different roles and status
– Multilingual system• Supports as many languages as required without changing the database
– Interoperability• Use of common formats and exchange protocols
• Simple data management by multiple users having different roles
• Multilingual system• Fully interoperable with the central BCH website
30
General concept: Object-relational database
–
Decision
Law
LMO
CompetentAuthority
Organization
Related LMO
Competent authority
Contact
Name
Legal basis
Person
Person
Organisation
32
Role and User Authorization
Role Description Authorization Writing
access
Anonymous Unknown user, anybody View published elements No
Member Member of a group, ID with username and password
Like anonymous,
Can read specific published elements of a group
No
Author Member of an entity entering data in the database
Like member
Can create, modify or submit new elements
Yes
Editor Member of an entity controlling data quality
Like author
Publish or reject elements
Yes
Administrator Person responsible for the central administration
Like editor
Management of users, groups and folders
Yes
Super Administrator
Responsible for administrative operations during installation of the system
Create top levels groups No
33
Status and Workflow
Status Description Process (Role) -> New status
Open Content of element open for changes, work in progress
Submit (Author) -> Submitted
Publish (Editor) -> Published
Delete (Author) -> Deleted
Submitted Element editing completed. Waiting for the release by the Editor
Publish (Editor) -> Published
Reject (Editor) -> Rejected
Retract (Author) -> Open
Rejected Rejected by the Editor (quality control)
Like open
Published The element is published and cannot be modified
Expire (Authot, Editor) -> Expired
Delete (Author) -> Deleted
Retract (Author, Editor) -> Open
Expired Old version not valid anymore Retract (Author, Editor) -> Open
34
Worflow
• Access control by role and element status
Role of users
•Anonymous•Member•Author•Editor•Administrato
r
Role of users
•Anonymous•Member•Author•Editor•Administrato
r
Element status
•Open•Submitted•Rejected•Published•Expired
Element status
•Open•Submitted•Rejected•Published•Expired
Quality controlQuality control
35
Decentralized management of the data
Federal Office of Public HealthFood Federal Veterinary Office
Animal vaccines
SwissmedicGene therapies, medicaments,
vaccines
Federal Office of AgricultureFeed, seeds, fertilizers, pesticides
Swiss Agency for the Environment,Forests and Landsacape
Field releasesBCH Focal point
Author
Author Author
Author
Administrator
Central Database
SCBDCentral BCH portal
36
Language
• Multilingual system– As many languages as required– No change in the database– One master language (CH-BCH: English)– Translations through internal functions which
query an internal translation database– Translation database = Datasets in database
tables
37
Conclusions
• Multi users system• Information between many different partners
• Quality control– Information quality controlled by role and element status
• Multilingual system– As many languages as required
• Flexible system– Possibility of creating new elements for specific information
• Interoperability– Elements similar to the central BCH (common format)– Fully interoperable database with the central BCH
• Open source components– System based on open source components only
• Fully operational and interoperable since Jan 04
39
The CH-BCH as standard «exchange of information tool» for interested countries
http://www.ch-bch.ch
40
The CH-BCH as standard «exchange of information tool» for interested countries
• 2 options:– Option 1: Full transfer of the system– Option 2: Supported transfer
41
Option 1: Full transfer of the system
• Entire system is provided
• The receiving country installs and runs the full application
• Swiss role:– In place installation help– One time training of people on the system– Further help available by email
42
Option 1: Full transfer of the system
• Conditions/requirements– Technical:
• Stable Internet connection• Server with security facility
– Know-How:• Linux operating system• Server software (Apache)• Security technology• ZOPE knowledge (basic, better with Python language)• HTML knowledge
43
Option 1: Full transfer of the system
• Advantages– Country is independent– Data and databases are locally stored
• Disadvantages– High technical facilities and knowledges needed– High initial input (material, training)– Long term viability
44
Option 2: Supported transfer
• Entire system is available
• System installed (hosted) in Switzerland– Technical and training support is provided– Help available by email
• Management of data by receiving country
45
Option 2: Supported transfer
• Conditions/requirements– Technical:
• Reliable and stable Internet connection
– Know-How:• No special IT knowledge needed• Short training course for users
46
Option 2: Accompanied transfer
• Advantages– No needs for high-tech hardware or IT knowledges– Only stable Internet connection required– Short training of users sufficient
• Disadvantages– Data are physically stored in Switzerland– This condition could be viewed as a starting solution– At anytime, databases can be transferred back to the
country of origin
47
National Database Templates for the Biosafety Clearing-House Application
(NDT-nBCH)Overview of the US nBCH Applications
48
Discussion Topics
• Introduction
• Development Goals and History
• About the Templates
• Hardware and Software requirements
• Steps in Developing a National BCH
• Discussion of Help Available
49
Introduction
• Secretariat of the Convention on Biological Diversity (CBD)– Developed a Simple National Biosafety Clearing-House
Application (nBCH)• Enter and retain Protocol information locally• Internet access not required to use the template
• National Biological Information Infrastructure– Developed National Database and Website Templates
• Leveraged experience from US Site development• Leveraged work accomplished by the Secretariat
50
Development Goals
• Increase functionality of the CBD Simple Database product based on the US experience
• Maintain compatibility with original CBD to ensure proper data transfer process
• Work with CBD and UNEP for review of compliance
• Create Exhaustive User Documentation• Add Website templates for a assistance in
developing a national website• Add Multilingual support to both database and
website templates
51
Development History
• Analyzed the flow of information during the U. S. Biosafety Regulation Process
• Applied new data model to the CBD’s BCH Simple National Database tool
• Reorganized and reconstructed data entry forms to follow flow of data entry process
52
The Templates: Target Users
• Target Users of the templates are Organizations that– Are in the technology startup process– Have with limited technical resources– Use Microsoft platform for desktop and/or web server– Range within the full spectrum of Internet connectivity
options• No Internet• Slow, unreliable, or costly Internet• Fast and reliable Internet
53
The Templates: Goals
• Goal of the templates?– Fast: Provides a Quick Start basis for initial development– Easy: Can be used in the initial data gathering phase
prior to reporting data– Scalable: it should be able to be moved to a server
platform if needed
• NOT the goal of the templates?– This is not a Production ready system– Will need assistance by an organizations system
administration and network security to go into Production
54
The Templates: Features
• Will run locally (no Internet) or will connect to BCH– (internet access required)
• No changes have been made to the CBD data transfer software
• Streamlined for less repetitive data entry• Extensive Help documentation
– Help within the Fields and forms– Documentation on Installation and set-up– Includes a Full-Users Guide
• Optional Web Templates:– Templates are fully customizable– Templates contain searching of database template content– Contain additional web content such as FAQs, Roles of the CNAs,
and Overview of the National BCH
55
The Templates “On top” Design
• Original CBD tables and data element formats retained
• New functionality added “on top of” original design
56
The Templates: Design Comparisons
57
Hardware & Software
• Simple installation of Database– Minimum configuration
• Personal computer• Windows XP, Win2000, ME, or Win98• Web browser software (for using help files and user documentatoin)• Method of writing data to electronic media, or printing for facsimile
transmission, or access to email
• Full Installation of Database– Minimum configuration (above)– Basic Internet connection (Dial up) or – Sustained Internet connection (Network)– Simple Object Access Protocol (SOAP) client for connectivity with
BCH (Installation instructions include in documentation)
58
Hardware & Software
• Installation of Website templates of Database– Full Installation of database requirements, plus– Web Server running Microsoft IIS – HTML Editor to modify templates
59
Steps in Developing a National BCH
• Phases of Technology Implementation
– Phase I• Data gathering• Use Database template: Install of database templates• Send data directly to Secretariat or register data directly in the Management
Center (based on capabilities)
– Phase II• Work with Information Technology (IT) Department• Analyze system requirements for type of Interoperability (Push or Pull )• Become Fully Interoperable
– Phase III• Work with CNAs, NFP and and IT departments• Refine Web Content• Create National website presence of BCH for public information
III
III
Pha
s e
60
Help Available?
• Bug Fixes and new versions– Latest downloads available from US Site– Multi-lingual version in beta testing now, production by
August
• Email Support– Email is advertised on all documentation
• Phone Support– Phone support to UNEP Regional experts by US
development team– UNEP Regional Advisors responsible for country level
phone support.
61
Help Available?
• Regional Workshop Support– Participate in all UNEP Regional Workshops
aimed at training technical experts in the use of the templates
• Country Level Support– Funding to attend a limited number of Country-
Level Workshops to provide hands on technical support