Science on Drupal Code Sprint - Winter 2015 - Semantic Web

Events happening in the community are now at Drupal community events on www.drupal.org.
dbassendine's picture
Start: 
2015-01-08 13:30 - 18:00 America/New_York
Event type: 
Sprint

Join us to help improve Drupal for the science community!

Do you have a great idea you'd like to see happen, or a bugbear that needs to be fixed? Would you like to help streamline a key framework for science collaboration, communication and data portals?

If so, bring your ideas and skills along to our sprint session on Thursday 8th January at the ESIP Winter Meeting in Washington DC (http://commons.esipfed.org/2015WinterMeeting) - either in person or online. Users, coders and writers are all needed and welcome!

  • Before the sprint - tweet us your ideas under #SoDsprint and we'll add them directly to our sprint Trello board at https://trello.com/b/QX23p1bp
  • On the day (1/8) - join us in person in Dupont, or remotely via Webex (details) or IRC (#drupal-science), for our Open House (10:30 - 12:00) to submit ideas, or our Code Sprint (13:30 - 18:00) to help implement them

This time around, we'll be focusing particularly on Semantic Web tasks, although other ideas are welcome.

Look forward to seeing you there!

Comments

PROV-O support in RDF

ashepherd's picture

I have a suggested topic for adding support for tracking provenance across a Drupal sites entities using the PROV-O ontology (http://www.w3.org/TR/prov-o/) with the RDFx module.

Use Case: For data repositories the issue of recording provenance of datasets as they change is very important when considering data citation and publication (which version of the dataset was used). PROV-O provides a structure for describing activities that occur on entities and the agent that triggered it.

I'll add this to the Trello board.

Thanks!

dbassendine's picture

Thanks Adam!

Could you add an d.o issue for this request at https://www.drupal.org/project/issues/rdfx and then comment back with the URL or Issue#?

If you have any initial ideas on how this might be implemented, include them on the d.o ticket. Otherwise, we can slate this in for architecture work.

Flagging issues for the sprint tomorrow

dbassendine's picture

If would like to flag issues for us to look at during the sprint tomorrow, here are the channels you can use:

  1. Send us a tweet tagged with #SoDsprint
  2. Log on to IRC #drupal-science (see https://www.drupal.org/irc/setting-up) and ping us with your request
  3. Comment on this thread
  4. Bring it to us in person during the Open House at the #ESIPFed meeting tomorrow

We will moderate requests and then add them to the sprint board.

Every request should include:

  • URL of the corresponding issue ticket on drupal.org - but if the ticket doesn't already exist, we can help you create it.
  • Rationale - briefly describe why the issue is relevant to the science community, and how it could be applied

To help sprinters tackle tasks effectively on the day, the drupal.org issue tickets themselves should be as descriptive as possible. Follow drupal.org guidelines for reporting issues and include background resources to help sprinters get up to speed, then reproduce, test and resolve the issue quickly and efficiently.

Thanks! David

Participating in the sprint tomorrow

dbassendine's picture

If you'd like to take part in the sprint tomorrow and help us tackle issues of relevance to the science community - you can join us at 13:30:

Before the sprint, make sure you have set up accounts on:

Have your usernames handy and send them over to me via IRC or Webex on the day. I'll then add you to the Trello board.

Thanks! David

Preparing for Drupal contribution

dbassendine's picture

To prepare your systems and skills to contribute to Science on Drupal tomorrow, you can follow the Drupal Ladder (http://drupalladder.org). Starting with the most basic setup, each rung of the ladder offers a step-by-step tutorial that brings you closer to being ready to contribute.

Take a look at the Module Contribution ladder (http://drupalladder.org/ladder/158c7cc7-1545-e674-e16a-c93af467e4c8). By type of work, here are the rungs you should have mastered to contribute to the code sprint:

  • PM or Docs - 1 Getting started in the issue queue; 2 Install Git; 3 Install Drupal locally
  • Tester - 1, 2, 3 and 4 Test Patches
  • Coder - 1, 2, 3, 4 and 5 Write a patch

Remember - if you're having trouble with any of these we can help you out on the day.

Thanks! David

DataViz issue for Charts module

dbassendine's picture

Here's an interesting issue in Charts module that needs testing: https://www.drupal.org/node/1237096

It allows charts to use a continuous X axis for time series.

Science on Drupal

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: