conceptual design of tapipedia: pre-final version
TRANSCRIPT
![Page 1: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/1.jpg)
Conceptual Design of TAPipediaPre-final version after feedback & comments
Nikos Manouselis, CEO [email protected]
![Page 2: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/2.jpg)
Background
![Page 3: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/3.jpg)
An extraordinary company that captures, organizes and adds value to the rich information available in agricultural and biodiversity sciences, in order to
make it universally accessible, useful and meaningful.
http://www.agroknow.gr
![Page 4: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/4.jpg)
TAPipedia
![Page 5: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/5.jpg)
TAPipedia
![Page 6: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/6.jpg)
“reference work or compendium”
![Page 7: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/7.jpg)
another Wiki-pedia?
![Page 8: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/8.jpg)
a repository?
![Page 9: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/9.jpg)
a search engine?
![Page 10: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/10.jpg)
a collaboration portal?
![Page 11: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/11.jpg)
my work
• understand context of work & operation• propose, explain, defend, adapt design
principles (the real thing)• write a Conceptual Design report (138 pages,
OK – not carved in stone)
![Page 12: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/12.jpg)
The report
(what I would like you to endorse and pay me for)
![Page 13: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/13.jpg)
ToC
I. Study Requirements– content / user/system
II. Conceptual Design of TAPipedia– high-level architecture– key components + interface
wireframes
III. Knowledge OrganisationIV. Software Technology Choice
![Page 14: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/14.jpg)
input on requirements
• 2012 TAP stakeholder consultation recommendations
• Regional assessments carried out by TAP partners • ToR on Conceptual Design by TAP Global Task Force• Feedback on first ideas from TAP CD Expert Group
(CDEG) at Montpellier• Feedback on initial report during Webinar of 18/6• Open commenting period until last week
![Page 15: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/15.jpg)
categories
a) user requirements (“Which stakeholders & roles should be the primary audiences of TAPipedia?”)
b) content requirements (“What information should TAPipedia include?”)
c) system requirements (“Which key services & functionalities should the TAPipedia software provide?”)
![Page 16: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/16.jpg)
priorities from Montpellier
1. To help TAP members and local stakeholders to discover methods & tools that will help them identify and assess emerging capacity development needs for AIS (inc. knowledge from other regions)
2. To help TAP members to present, explain and communicate the framework on CD for AIS so that it may be easily adopted & implemented
3. To help local stakeholders share their own applied and context-specific AIS knowledge that addresses the needs of their stakeholders
![Page 17: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/17.jpg)
design principles
1. “Standing on the shoulders of giants”– take advantage of what TAP partners are doing
(and/or paying for)– map, enhance discoverability, link resources to
each other
2. Open, modular architecture– built to collaborate & inter-operate– easy to plug content+services in (and out),
extend and expand
![Page 18: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/18.jpg)
high level technical architecture
Regional/local knowledge sources
TAPipedia index
Regional, local & other knowledge sources & collections on CD for AIS
Regional/local knowledge sources
TAPipedia indexRegional/local
knowledge sources
TAPipedia index
Knowledge sharing services
Knowledge discovery services Knowledge authoring services
Knowledge repository Analytics dashboard
![Page 19: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/19.jpg)
Positioning & links to other platforms
e.g. GIZ, USAID, EMBRAPA, …
Variouscommunity & collaboration platforms
TAPipedia index
e.g. CG centers, CATAS, Agrinatura, …
e.g. AGRIS, AGRICOLA, SIDALC, …
Various marketplace platforms
…
![Page 20: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/20.jpg)
recommending (agri)Drupal
• avoid going for developing TAPipedia using different software systems– rather focus on one core software platform for
core knowledge management– take advantage of existing, working platforms
• select a popular and well-supported system that can provide most of the required functionalities, using existing open source modules
![Page 21: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/21.jpg)
Proposed implementation steps
A first prioritisation, for discussion
![Page 22: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/22.jpg)
Phase I: autumn’15
• set up TAPipedia index & carry out mapping of TAP partner resources [Sept’15]
• develop Knowledge Sharing services to help manage & curate TAP partner contributions [Oct’15]
• develop Knowledge Repository & initial version of Knowledge Discovery service [Nov’15]
• revamp TAP web site, include deployed components, launch TAPipedia alpha [Dec’15]
![Page 23: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/23.jpg)
Phase II: spring’16
• deploy Knowledge Authoring services to support online presentation of CD for AIS framework [Feb’15]
• transfer operationalised forms of framework into their online formats, develop Analytics Dashboard [March’15]
• integrate into deployed components, develop additional language versions, launch TAPipedia beta [April’15]
• testing & documentation period; operational launch [June’16]
![Page 24: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/24.jpg)
To discuss further
![Page 25: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/25.jpg)
(my) Points to consider
1. Positioning TAPipedia2. Making TAP partner activities visible
through TAPipedia3. Running TAPipedia
![Page 26: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/26.jpg)
1. Positioning
• Not as a competitive IT platform to existing ones, but as an open platform that may catalogue & syndicate content
• Using existing systems for parts of the job that are marginally in scope or that have high cold-start & maintenance cost– e.g. community platform, online marketplace?
![Page 27: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/27.jpg)
2. Visible TAP partners
• Cataloguing & pointing to CD for AIS interventions, resources, case studies that partners want to showcase
• Carrying out an online mapping of relevant resources & interventions– Call to Action to TAP Partners
![Page 28: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/28.jpg)
Running TAPipedia
• Expected to need a number of teams to operate activities around TAPipedia– Editorial Team, Online Framework Authoring Team
(incl. local teams), Online Community Facilitators• Tasks & workflow of TAP secretariat; support &
engagement of TAP members
![Page 29: Conceptual Design of TAPipedia: pre-final version](https://reader036.vdocuments.net/reader036/viewer/2022081516/55c388bfbb61eb90318b4639/html5/thumbnails/29.jpg)
…more?