1 / 18

P roject management tools

SeaDataNet Technical Meeting Project management tools Extranet, Mailing lists, Project documentation. P roject management tools. SeaDataNet web site www.seadatanet.org public area private area (extranet) : simple access control : only one login/password Project objectives

kalila
Download Presentation

P roject management tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SeaDataNetTechnical MeetingProject management toolsExtranet, Mailing lists, Project documentation

  2. Project management tools • SeaDataNet web sitewww.seadatanet.orgpublic areaprivate area (extranet) : simple access control : only one login/password • Project objectives • Partners (points of contacts, …) • Description of Work • Meetings • Finalised documents (applicable version) and software tools • Mailing lists • One list per group (technical, …) owned by the chair person + one general list (include sub-lists) + user desk (SeaDataNet users point of contact) • Based on Sympa software • Document management • Based on BSCW software (Basic Support for Cooperative Work - Germany) • Cooperative work on documents (non finalised versions) and software • Other functionalities (agendas, tasks, …) : probably not used within SeaDataNet

  3. Available mailing lists • Mailing lists available on seadatanet.org • sdn-stcom : SeaDataNet steering committe members • sdn-coord : tealmleader of each partner (as recorded in the A2b form) • sdn-advisory : SeaDataNet advisory group • sdn-tech : SeaDataNet technical group (our group) • sdn-ta : SeaDataNet transnational activities (data management) • sdn-balticsea : partners from the Baltic Sea • sdn-northsea : partners from the North Sea • sdn-atlantic : partners from the Atlantic • sdn-medsea : partners from the Mediterranean Sea • sdn-blacksea : partners from the Black Sea • sdn : all people + VIP (officers, directors, …) • These lists are private(to discard spam)i.e. usable only by people who belong to the list • sdn-userdesk is the SeaDataNet users point of contact

  4. How to use SeaDataNet mailing lists • To send a message Use the mail adresssdn-listname@seadatanet.org i.e.sdn-tech@seadatanet.org, sdn@seadatanet.org, … • To retrieve all email addresses recorded in a list Mail to sympa@seadatanet.org with the following command (in the mail body) REV sdn-listname • To manage a list (only for list owners : i.e « chairpersons » of groups) Mail to sympa@seadatanet.org with one of the following commands (in the mail body) : • To add a user’s adress in a list ADD sdn-listname user@host UserName – Organism • To delete a user’s entry from a list DEL sdn-listname user@host • To subscribe to a list (subscription is subject to approval by list owner) Mail to sympa@seadatanet.org with the one of the following command (in the mail body) : SUB sdn-listname youradress@host YourName – Organism

  5. BSCW : Basic Support for Cooperative Work • Secured access (according to SeaDataNet rules discussed later) • Upload & Download of documents, pieces of software, … • Version management (from several people) • Reviews and comments on documents • Directories and sub-directories • SeaDataNet (root directory) • sdn-tech (technical group) • sdn-advisory • … • Subdirectories may be created if needed • Access via SeaDataNet web site • Interface adapted to current language of Web browser (english by default) • Cache option must be turned to « Every time » • Cookies must be enabled  • Description of BSCW functionalities available athttp://www.bscw.de/index_en.html • If problem : bscwdba@seadatanet.org or bscwdba@ifremer.fr

  6. Add a sub directory How to use BSCW? Add a file(file upload) • Actions on document : • add a comment, • replace by a new version • … Click on file name : File download

  7. SeaDataNetTechnical MeetingEuropean research vessel Directoryand others platforms (buoys, floats, observatories)

  8. European Platform (Vessel, …) Directories :Identified needs • Two main objectives • Controlled vocabulary on platform names • In service or historical research vessels • Ships of opportunity • Other platforms (Buoys, Floats, Satellites, …) To be used within Discovery Directories and Services • Cruise Summary Reports (CSR) • Ocean-observing System (EDIOS) • Common Data Index (CDI) • Platform description limited to a small number of fields • Mandatory : Unified code, Name (if exists), Country (Flag), Ship owner, • Alternate key codes (Call Sign, WMO code, …), • Optionnal : Max speed, … • Research vessel meta database • Only in service research vessels (as part of the European marine research infrastructure) To propose advice to marine research « administrators » • MarinEra, OFEG, … • Full description required • Vessels characteristics (field of activity, range of action, …) • Onboard available equipments, …

  9. European Platform (Vessel) Directories : What exists? • ICES vessel directory • include Ships of Opportunity (VOS) • compatible with (managed with) WDC – Washington http://www.ices.dk/ocean/ (items Code / ICES Ship codes) 35AY ALIS callSign FHQB 35AZ P. AZEN 35B2 BEG HIR (FQND) 01/01/1994 35B3 BREGTAGNECall sign: FNBR IMO number: 8707329 ICES created 100205 35B4 BORDA Call sign: FYCT Navy ship (ICES added 030206) 35BA BORHA II 35BB BEAUTEMPS BEAUPRE (FABB) 2003/2004-on. (Also old 35BB launched 1939) • EurOcean vessel directory • focus on in service research vessels • full description for European Infrastructure (MarinEra, …) • ARGO, DBCP, VOOS within the framework of JCOMM • WMO codes for buoys and floats • aims to be unique, managed by JCOMM/OPS

  10. European Platform (Vessel) Directories : Issues within SeaDataNet • Ensure consistent entity definitions across both databases • Common vocabulary for ships : ICES directory • Complete information on existing research vessels : EurOcean • Other platforms : JCOMM/OPS • Establish a linkage key between existing databases • and user interface to use these links. • Continuous management and cleaning • multiple ships have carried the same name • ships have changed name • inputs and updates from partners

  11. SeaDataNetTechnical MeetingSecurity and monitoring servicesAuthentification, Authorization and AdministrationTools for NA2

  12. Security and monitoring Services • Seadatanet Monitoring • Statistics on usage (webstat) • System monitoring • Authentification, Authorization (Access rights) • Partners • Control access to online tools (direct metadata typing, ….) • SeaDataNet users • Access to metadata (EDMED, EDIOS, CSR, CDI, …) freely available(information, location maps, …) • Access to data : controlled • Distributed data repositories • Data policies are not identical • Objective : SeaDataNet seen has a virtual private network only one login/password must be known per user !

  13. SeaDataNet Monitoring • Statistics on contents • Done by NA & TA • Statistics on usage • Number of hits, • Number of visualized information pages (metadata), • Number of data queries, • Delivered datasets Statistics computed by each component of SeaDataNet Consolidation at SeaDataNet coordination level Monthly transmission (ASCII files) • System monitoring… toward a system ran operationally (SeaDataNet V1 & V2) • Availability analyses • Component failures Must include internet links(access through internet like users) Monitoring software which tests if response of centre servers(polling of servers, as a start point, could be a simple shell script)

  14. Authentification, Authorization • Real VPN can not be established between SeaDataNet partnersseveral network providers and VPN solutions are vendor dependant • SeaDataNet must set up its own solution! • role of identified person : need of user directory attribute(s) partner, chief scientist of a cruise, academic user, research user (involved or not in a related project), … • Centralized authentification • Only one directory • Maintain by user desk • Consistency easy to maintain !Only one login per person • Simple if access only checked by one entry point (i.e. SeaDataNet portal) • Distributed authentification • Several user directories(one by centre) • Users may be identifiedin several centres • Already done! • Single sign-on system(s) • Semi distributed system • Only one user directory – One or several servers • Minimal pre-requisite from existing systems (proxy mechanism) • Could be also directly used in software (PHP, Java, …) • Used by NERC Data Grid (Globus toolkit) & IFREMER (CAS – Yale University)

  15. Single sign-on mechanism CAS (Central Authentication Service from Yale University)example Login request (HTTP) Authentification form (HTTPS) Single Sign-On Server User web browser

  16. Single sign-on mechanism Request to user directory(user directory protocol) Login / Password Authentification (HTTPS) TGC (cookie) User web browser Single Sign-On Server User directory(LDAP server, …) TGC : Ticket granting cookie (session identifier)

  17. Application software(SeaDataNet system) Single sign-on mechanism Single Sign-On Server ST Authorization query Validation Redirect (Proxy) Request answer Authentification (HTTPS) ST Authentified request User request (non authentified) ST TGC ST : Service ticket(usable only for one request) User web browser

More Related