Recommended
Recommended
More Related Content
Similar to Progress Report, October 2011
Similar to Progress Report, October 2011 (20)
Recently uploaded
Recently uploaded (20)
Progress Report, October 2011
- 1. GBIF‐NPT Nodes Portal Toolkit Bruno Danis, Global Nodes, Buenos Aires, Oct 2011 1
- 2. Layout of this session • Background • Update on the progress of the NPT • Approach for development • Examples • How to progress further • QuesMons and open discussion 2
- 3. A history of NPT • Need idenMfied Oct 2002 • First release Dec 2002 • Deployment of DiGIR network 2004 • NPT as ranked priority Oct 2004 • DraQ requirements doc Oct 2005 • Early prototype Apr 2006 • Online survey 2009 • NPT Advisory Group Dec 2009 • NPT kickoff Nov 2010 • NPT AG‐workshop Mar 2011 3
- 4. Two ObjecMves • Deploy, maintain, extend Biodiversity portals: NaMonal, ThemaMc, Regional • Pla[orm for technical developments by and within GBIF Community 4
- 5. Progress made • Capture Scope and Requirements • Develop communicaMon channels • Define SoQware Requirements • IdenMfy complimentary approach • Delineate High‐Level Architecture (NPT1) • IdenMfy Do‐ers (NPT1) • Start Development of Phase 1 5
- 6. A dual approach • Diversity of needs and constraints • Time constraints • High‐demand • NPT1, NPT2 • Flexibility, Extensibility and ReacMvity 6
- 7. NPT1 • Fast development, fast web‐presence • Focusing on nodes with low/no IT capacity • Basic needs • iniMate interoperability with GBIF webservices • Framework: Drupal7 • On the shoulders of Scratchpads2/ViBRANT 7
- 8. FuncMonaliMes (end users) • View taxon details/export checklists • View/export distribuMon map • Search portal • Select language • View metrics • Blog/news 8
- 9. Drupal 7 • Chosen framework • Why? – Strong Open Source community – Already taken up by Scratchpads, EoL LifeDesks, EDIT, LTER, iOBIS – flexibility and extensibility embarked – Ready to go. 9
- 10. NPT1 Modules 10
- 11. NPT2 • encapsulates NPT1 + GeospaMal component • process, manage, visualize data • Framework: Drupal7 • FoundaMon: SP2+NPT1+GeoSpaMal component (in or out Drupal, TBD) • iOBIS portal 11
- 12. FuncMonaliMes (end users) • All NPT1 funcMonaliMes+ • Advanced filter building (build/save/retrieve) • View/download data • View interacMve map • Toggle spaMal layers 12
- 13. iOBIS • InternaMonal Ocean Biogeographic InformaMon System • new webportal for all Marine Biodiversity • Drupal6 + GeospaMal component • Has the needed funcMonaliMes and more • ReacMve, reliable even under stress • Community development • A showcase for NPT (but over‐specified) 13
- 16. MulM‐resoluMon maps 5 degrees 0.5 degree 1 degree 0.1 degree Humpback whale as an example
- 17. Higher taxa with/without branches Including branches Excluding branches Annelida as an example; By default, the distribution map for a higher taxon includes observations for branch taxa.
- 18. Extract data with addiMonal layers Humpback whale observations in Bahamas EEZ
- 19. Browse taxonomic tree Selecting a taxon brings up taxon information to the right panel
- 20. MulMlanguage support Español (Spanish) Simón Bolívar (Japanese) Duke Univ. русский (Russian) Nat’l Academy of Sciences of Ukraine More to come…
- 21. How can Nodes contribute? • Get on with Drupal 7 (now) • Test NPT1 (around April 2012) • Test NPT2 • Tweak NPT1&2 • Suggest/develop/implement/share new modules • Scout and share modules/funcMonaliMes using exisMng pla[orms • Help idenMfy new needs: requirements, capacity building, mentoring, funcMonaliMes,... • Help with translaMon of interface(s) 21
- 22. Next steps • Architecture refinement NPT1+NPT2 • NPT1 modules development and integraMon • IniMal tesMng • NPT1 deployment • TesMng phase • NPT2 modules development and integraMon • NPT2 GeospaMal component development and integraMon • IniMal tesMng 22
- 23. To sum up... • A long history, a community project => an ecosystem of wishes • Not one soluMon fits all needs (wishes) • Dual approach NPT1/NPT2 • We’re ready to kickstart development 23
- 24. Find out more • Google Code site (official stuff) • NPT Blog (general info) • NPT Mindmap (for the enthusiasts) • GBIF community site • Contact me: bruno.danis@gmail.com 24
- 28. NPT Mindmap 28
- 29. Thanks! • NPT‐AG: the Advisory Group • BeBIF: the Belgian BIF • NPT‐TTF: the Technical Task Force • Sylvain: my IT guru • MGEL: the Marine GeospaMal Ecology Lab (Duke University) • GBIF‐S: the GBIF Secretariat 29
- 30. QuesMons? 30
- 31. Discussion • Nodes parMcipaMon • Priority installaMons • HosMng • PotenMal developers/scouts/mentors • IntegraMon with other GBIF components (ORC, Community, Data Portal,...) • The long term 31
- 32. The next concrete actions will be taken to kick-start the development phase of NPT1. Timelines in the chart below are indicative. Items for which help from the GBIF (tentaMve) Timetable Community will be required are in red. Oct- Nov- Dec- Jan- Feb- Mar- Apr- May- Jun- 11 11 11 12 12 12 12 12 12 NPT1 Architecture refinement NPT Modules development and integration Initial testing NPT Deployment Testing phase Initial NPT instances NPT2 Architecture refinement NPT Modules development and integration NPT GeoStack development and integration Initial testing 32
- 33. NPT1 maps National map for each taxon Global map for a taxon Global map for data provided by country 33
Editor's Notes
- \n
- \n
- \n
- \n
- Make the point here that, with the Advisory Groups tried their best to picture the need of nodes, given it's a heterogeneous network we are, one software is not going to fit all. But we've already have the flexibility and extensibility in mind to conduct the whole process from now on.\n
- Carefully explain the 2 products here. NPT1 will be just focusing on basic need of national nodes that have no IT capacity at all, which will have\nfunctionalities that we only briefly illustrated here. The development of NPT1 will introduce necessary modules to talk to GBIF web services, which will be used in NPT2.\nEncapsulating the modules and profiles of NPT1, NPT2 will introduce geospatial components that allow nodes to process, manage and visualise biodiversity data directly within the NPT. Details like OpenGeoStack shouldn't be mentioned until people/developers are asking, showing iOBIS.org and emphasizing their result is something could be taken into NPT, is enough.\n\n
- \n
- \n
- 3. Drupal is the chosen framework to enable community-driven development.\nWhy? and How can community development take place around it.\nWe need to pick one and we must have an agreed framework to kick-start and work together.\nDrupal is a PHP website building framework. After 10 years development, Drupal now is a strong open source community, which has almost 12 thousand modules and maintained by 10 thousand developers worldwide, that includes biodiversity community like ScratchPads, LifeDesks, EDIT and LTER. So we not only have something relatively easy to start, but something READY to start.\n\nPHP language is easier for nodes to develop its IT capacity, given that it is widely used for building websites[1] and has a lot of learning resource available for beginners. Drupal has a coding convention and APIs that PHP developers can easily follow.\n\nWhat is the difference of Drupal?\n\nDrupal is a joint effort coded with flexibility and extensibility in mind. Before the existence of frameworks like Drupal, websites built with predefined specification usually serves the original purpose very well, but as the project evolves, if the site is built from scratch without using a common framework, often code refactoring will be required, which means inevitable costs in breaking and rebuilding. Things are worse if only a few people know how the site was built.\n\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- How nodes should contribute?\nWhile the core NPT development is running, nodes are invited to learn to use Drupal. Drupal requires some learning curves, but that pay later when nodes find it's flexibilities, even before being able to code for it.\nWhen more and more coding details are revealed on the NPT project site, nodes are invited to test using it, and are absolutely encouraged to tweak it and let other nodes know you are coding for it.\nWith core NPT modules in place, and with Drupal expertise in the nodes community, when nodes tweak the tools to fit themselves, we can always ask others to suggest a module, and usually there is an answer.\nStressing this last point is very important. We should get a good feel of how many nodes could and are potentially willing to participate actively in the development of the NPT. Also clues on the amount of uptake by Nodes is necessary. We have to see how we can advance this during the discussions at the NPT session. But we cannot stress too little this is a community project, and therefore active involvement is needed. We need strong arguments to reserve a substantial amount of money towards the NPT in 2012.\n\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n