17 May 2016: Meeting Summary

1 17 May 2016: Meeting Summary

Agenda

Technical Work- Stuart Sutton
Resource Collection- Sean Dolan
Editorial Board- Tom Baker
Marketing and Community Building- Mike Lauruhn

Summary

Present: Joseph Chapman, Mike Crandall, Abi Evans, Mike Lauruhn, Sam Oh, Stuart Sutton, David Talley, Marcia Zeng

Technical:

Abi building out saved sets addition; should be done in next few days after discussing with David. Joseph continuing to work on authentication for resource authoring, and will do the update on the revised Competency Index once Stuart gives go-ahead (in next day or two). David has added a "contact us" form that is now operational. Will move onto learning maps as next (and final) deliverable.

Resource Collection:

Sam is working on learning resources, may have some ready at end of June. Mike will follow up with Sam on possibility of including some Topic Map resources in the collection and the Competency Index.

Editorial Board:

Editorial Board met last Friday, and approved new competencies developed over last two calls. These are reflected in a new Google Doc^[1] that is open for comment. Stuart used the ASN editor this weekend (and is rechecking because of multiple changes to the index) to transfer these changes so that David and Abi could refresh the published version^[2]. To do this, Stuart works through "diffs"^[3], and enters the changes in the ASN editor manually. The process, which is documented here^[4], is reasonably simple and straightforward. However, it does presuppose

- A "source editor" (currently Tom), who: 1) understands how the process works, 2) can edit the source files, 3) can run `make`, which runs the Ruby script, which requires:* prior installation of `ruby`, * prior installation of `pandoc`, 4) can commit files to https://github.com/ld4pe/cieb/blob/master/CompIndex/README^[5], and 5) can communicate the URL to...
- A "production editor" (currently Stuart), who 1) can use ASN to manually update the competency index in the ASN editor, and 2) can communicate to
- A "webmaster", such as David or Abi, who can update the website with the latest version of the Competency Index in the ASN editor.

The major activity that requires hand-generation is the creation of the Google doc for public comments- the hope is that eventually some other mechanism can be found for commenting. Moving from Github to public comment is the difficult piece of the process. The closest successful analog for the community-driven development of a vocabulary is Schema.org. Like the source for the Competency Index, the Schema.org vocabulary is posted on Github^[6]. As the next step, the Editorial Board will propose a way to adapt the Schema.org process^[7] to CIEB.

One of the goals of the last CIEB meeting was to look at gaps, to find areas where no competencies are available. Want to fill these in- very close to having full competencies. May not have benchmarks for all, but will have fully populated competencies by the next build in June. Thorough coverage of benchmarks under SPARQL, less complete elsewhere. They would like to fill out as many of the following gaps as possible:

- Expressing provenance of Linked Data
- RDF data analytics (with help of an appropriate expert?)
- Approaches to persistent identifiers
- SPARQL endpoints
- Triple stores
- Non-RDF linked data (note lowercase) - eg, Microdata, graph databases (Neo4j)

The Competency Index Editorial Board plans to hold at least two more teleconferences before the summer -- June 3 and June 24. The goal will be to declare Competency Index Version 1 by the end of June. Two final teleconferences will be held in September and October to wrap up any loose ends and, ideally, to test a Schema.org-like approach to maintaining the Competency Index.

Marcia notes that hierarchical browsing now means you have to have knowledge of the classification. Could consider adding search or indexed keywords as alternate entry mechanism- adding further filtering as a means to access content through facets, not just competencies and topics. This will have to be undertaken down the road after the initial project wraps up, but is worth keeping in mind. Can use existing metadata (learning resource type, interactivity type) as index terms, but probably won't be able to move beyond this in the current project scope. The underlying infrastructure is in place, but will need additional expansion to fully implement for access through aboutness. Might consider using blog posts to move this discussion forward, with links to saved sets or learning maps to facilitate discussion, since concrete examples will help ground in reality. May be something that Marcia's team can work on during user studies this summer. David and Marcia will follow up to discuss plan for user evaluation of site.

Marketing and Community Building:

Mike L will put up a blog post on the new CI for public comment this weekend. Earlier feedback asking for breaking up CI by beginner, intermediate, advanced or by job role has not been followed through on (see discussion above)- is there a way to provide response to input? Two mechanisms now for feedback- Google doc and partners in the field. Should all be going into Github as issues, but not happening now. Result is that some decisions are not recorded, and thus a gap in feedback results. Maybe there is a way to allow commenting on nodes in learning maps, might be worth exploring down the road.

Mike L will be on a full day NISO webinar on linked data next month (June 15), and will be talking about LD4PE as part of that. DCMI/ASIST events will have dates and times soon for workshop and special session. IFLA poster sessions will be on August 15/16.

Action items

Abi and David to finish saved sets function and go live
Mike to follow up with Sam on possible Topic Map competencies and learning resources
Stuart to finish reviewing CI revisions so Joseph can add to triple store and Abi and David can refresh website
David and Marcia connect regarding plan for site assessment
Mike L to put out blog post on revised CI for feedback this weekend
Stuart consult with Tom, David and Joseph about what to do with OCLC data set (from last month)
Next Meeting: Tuesday, 6/21/16 at 7:00 AM PDT.

2016-05-17

17 May 2016: Meeting Summary

Contents

Agenda

Summary

Action items

Meeting Resources & References