New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"OLI STACK" Inaugural Issue #128

Open
damg70 opened this Issue Aug 21, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@damg70
Contributor

damg70 commented Aug 21, 2015

The "Oli Stack" is an outgrowth of issue #79 and now has it's own tags, and a better name. @kuualoha is down with this.

Summary:

The original spreadsheets that document the places where various oli have been published went through an initial conversion into database-ready status. After an excellent meeting on 8/21/2015 (that introduced the Cortext project and Achievements) @kuualoha and I decided that the best use of this dataset would be based around being able to compare differences bewteen the chants' appearances, and to annotate them.

Instead of side by side comparisons (a-la Noelani Arista's Kanikau prototype,) we are going to experiment with an interface convention borrowed from Adobe Photoshop: layers. A given chant that shows up in multiple publications will be presented via stacked transparencies so that the viewer can compare line and word differences between their appearance. The user will be able to turn various layers on and off, and use the drop-down model to reveal the multiple versions of a given line. A note-taking field will be provided so that the registered I/O user can ... take and save notes. The system would log the current configuration of visible and transparent states.

A better design document is forthcoming.

Steps:

  1. Assemble definition of the fields that will describe each entry; @kuualoha you took a picture of our sketch: so this is the publication location, the name of the submitter, geolocation data, the year, any associated jpgs, etc. Please take a shot at generating the first set of fields.
  2. Create a set of appropriate database tables (under DAHI) on the server.
  3. Craft an admin front end for @kuualoha (and any students she recruits) to enter the remaining metadata for each chant. NOTE: We are not expecting all of the chants to go into the database during FA2015, but a handful that shows how the system would work in instances were there is only 1 version of a chant and multiple versions.

Goals:

  1. Deliver a working demo of the stack by end of semester, FA2015.

@damg70 damg70 added this to the Fall 2015 milestone Aug 21, 2015

@damg70 damg70 assigned damg70 and unassigned damg70 Aug 21, 2015

@damg70

This comment has been minimized.

Show comment
Hide comment
@damg70

damg70 Sep 1, 2015

Contributor

@kuualoha can you take a look at step 1 above and verify that we have all the necessary fields defined? I want to get started on step 2 so that you can count on step 3 being used in your classes this semester. Let me know what's up.

Contributor

damg70 commented Sep 1, 2015

@kuualoha can you take a look at step 1 above and verify that we have all the necessary fields defined? I want to get started on step 2 so that you can count on step 3 being used in your classes this semester. Let me know what's up.

@rcrath rcrath removed the in progress label Sep 9, 2015

@damg70 damg70 modified the milestones: Spring 2016, Fall 2015 Jan 7, 2016

@rcrath rcrath modified the milestones: Blue Sky, Spring 2016 Feb 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment