Your SlideShare is downloading. ×
0
Eol Shorthouse
Eol Shorthouse
Eol Shorthouse
Eol Shorthouse
Eol Shorthouse
Eol Shorthouse
Eol Shorthouse
Eol Shorthouse
Eol Shorthouse
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Eol Shorthouse

574

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
574
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Drupal Taxonomy Code Sprint <ul><li>Why? </li></ul><ul><li>How well does Drupal currently handle hierarchical taxonomies </li></ul><ul><li>What about multiple & extremely large vocabularies? </li></ul><ul><li>What about reconciliation (synonymy, relatedness)? </li></ul><ul><li>What about machine tagging? </li></ul><ul><li>What about Semantic Web? </li></ul><ul><li>Can we hook permissions/roles into selection of terms? </li></ul><ul><li>How well will our solutions integrate with search? </li></ul>
  • 2. Best Practices <ul><li>Google Code: </li></ul><ul><ul><li>Need a Google account </li></ul></ul><ul><ul><li>https://code.google.com </li></ul></ul><ul><li>Drupal CVS </li></ul><ul><ul><li>Patches: tag “EOL Taxonomy Sprint” </li></ul></ul>
  • 3. Who & Why <ul><li>You are leading this sprint & you will take ownership of where we take it </li></ul><ul><ul><li>You will submit patches to Drupal’s CVS </li></ul></ul><ul><ul><li>You will participate in Google Code svn </li></ul></ul><ul><li>We want to see D6 & D7 lead the way for CMS’ but many sites continue to make use of D5 </li></ul><ul><ul><li>Can we push for core solutions that can be back-ported? </li></ul></ul><ul><li>Can we push for flexible solutions that cut through idiosyncratic needs? </li></ul><ul><li>Can we develop or refactor existing modules if we cannot pave the way to development in core? </li></ul>
  • 4. The Encyclopedia of Life David P. Shorthouse Vitthal Kudal
  • 5. Biology-Centric, Drupal Solutions <ul><li>BugGuide </li></ul><ul><ul><li>Are not using taxonomy or views </li></ul></ul><ul><li>ScratchPads </li></ul><ul><ul><li>Use taxonomy as a mechanism to tag content with scientific names </li></ul></ul><ul><li>Many biological pursuits have chosen other CMS’ or Drupal workarounds ( e.g. Animal Diversity Web) </li></ul>
  • 6. EOL Approach <ul><li>Content aggregated from other biodiversity websites using client-produced XML docs </li></ul><ul><ul><li>Schema produced in-house using existing (Dublin Core) and emerging standards (TDWG: Species Profile Model) </li></ul></ul><ul><li>Front-end: Ruby on Rails </li></ul><ul><li>Back-end: MySQL </li></ul>
  • 7. Schema for Data Objects
  • 8. EOL Approach - Drupal <ul><li>Major participatory thrust: Drupal multisites (eventually standalone) called LifeDesks </li></ul><ul><ul><li>Three profiles: Expert, Citizen Scientist, K-12 </li></ul></ul><ul><ul><ul><li>December release: taxa-centric , LifeDesk: Expert </li></ul></ul></ul><ul><ul><li>Each have capacity to build “species pages”: </li></ul></ul><ul><ul><ul><li>Contents of which are atomized as nodes (e.g. chapters of text, images, videos, specimens, etc.) for storage </li></ul></ul></ul><ul><ul><ul><li>Aggregated for HTML representation (View? Template? Panel?) </li></ul></ul></ul><ul><ul><li>Each must produce an XML document using schema just as do existing biodiversity website partners </li></ul></ul><ul><ul><li>http://lifedesk.eol.org </li></ul></ul>
  • 9. Taxonomy Management <ul><li>Immensely important for the success of EOL’s LifeDesks, EDIT’s ScratchPads, and other biology-centric pursuits </li></ul><ul><ul><li>Editor is paramount to success </li></ul></ul><ul><ul><li>Reconciliation of terms is critical </li></ul></ul><ul><ul><ul><li>Drag & drop functionality between terms and synonyms & differentiation among kinds of synonyms ( i.e. objective synonym, subjective synonym, common name, language of common name) </li></ul></ul></ul>

×