You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Calls are held every Thursday at 1 pm eastern time (GMT-5) – convert to your time at http://www.thetimezoneconverter.com – and note that the U.S. is on daylight savings time.

View and edit this page permanently at https://wiki.duraspace.org/x/leMQAg, or use the temporal Google Doc for collaborative note taking during the call.

VIVO 1.6

  • VIVO 1.6 release standup meetings are held every weekday noon – likely primarily of interest to those committing code for this release, but open to all

  • Given the ontology and directory layout changes, should this be version 2?

    • Pros: this is a bigger jump than a normal point release, especially with the ontology and data migration, but also with the RDF initialization files rearrangement

    • Cons: there are other features we consider important for 2.0, such as completing multiple language support for content entry and editing and not just the menu and content display; this is the first release of the ISF/VIVO ontology and of internationalization so doesn't feel mature enough for 2.0
    • Road map consideration – we need an updated technology road map and defining goals, features priorities, and resource requirements for 2.0 might be the best way of framing that discussion

  • For background, see the  VIVO 1.6 release planning  or VIVO 1.6 JIRA issues and please comment there or here

Apps & Tools Working Group

Chris Barnes would like to talk to us about his plans for the new VIVO working group and get your input on topics, timing, and frequency of calls.

    •  Create list of goals and action items for working group
    • Decide on recurring meeting time.
    • Discuss creating working group Github site and NAME
    • Discuss finding the first 4 tools presenters for meetings.
    • Other / Updates

How do we discuss what should be included in core VIVO?

Jim has proposed and Stephen has echoed a desire to look at what we include in core VIVO.  Stephen makes the following points:

However, I don't think they should just flow in. I think they should get code reviewed and community approved.  This is for two reasons.  
    1. Some things should stay local, albeit very few things in my opinion.
    2. Everyone needs a little recognition sometimes, discussing contributed features helps us all understand who is working on VIVO and feel more apart of the community and not just users.
This isn't the vivo-user-group list, it's the vivo-dev-all list and we should embrace community contributions by discussing them in our meetings.

VIVO 2013 Conference

  • If you gave a poster or talk and it's not yet on the VIVO 2013 materials page, please send Tim Worrall your final copy or a link to SlideShare or similar online service, or add the link to this page or the Google Doc

Updates

  • Brown
  • Colorado
  • Cornell
  • Duke
  • Johns Hopkins
  • Memorial
  • RPI
  • Scripps
  • Stony Brook
  • Texas A&M
  • UCSF
  • Virginia Tech
  • Weill Cornell
  • anyone else

Notable list traffic

Restricting user access to data from named graphs (Eliza)
  • Jim is developing a wiki page on the Policy implementations that differentially govern authorization to edit anything in VIVO based on the class of the data involved and the level of privileges of the user, and Eliza will be looking at making a change that may look directly at the graph any given publication belongs to
VIVO Sparql endpoint requires login
  • (Patrick) At the moment, in order to issue a sparql query against VIVO, it looks like you have to actually be logged in. We want to be able to allow anonymous users to be able to issue sparql queries. I don't see anywhere in the documentation that details anything about configuring or managing the endpoint. Is there a way to allow anonymous users to issue sparql queries?

See the vivo-dev-all archive and vivo-imp-issues archive for complete email threads

Call-in Information

Date: Every Thursday, no end date

Time: 1:00 pm, Eastern Daylight Time (New York, GMT-04:00)

Meeting Number: 641 825 891

To join the online meeting

To join the audio conference only

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.