Difference between revisions of "Winter Quarter 2015"

From EBA_Documentation
Jump to: navigation, search
m
m
Line 51: Line 51:
  
 
'''From last week:'''
 
'''From last week:'''
 +
 
Chris to create a 3 person JSON object, update all Volume 19 XML files to current version, update PHP Textual Viewer, copy Volume 1 from Allison’s branch and create its own development repository, and begin transfer of content from Wordpress to Omeka
 
Chris to create a 3 person JSON object, update all Volume 19 XML files to current version, update PHP Textual Viewer, copy Volume 1 from Allison’s branch and create its own development repository, and begin transfer of content from Wordpress to Omeka
 
Tony is at roadblock with the Javascript version of the Textual Viewer. It was agreed that we should start a retreat back to the PHP viewer and move forward from there. The discussion was left at Tony was going to think about it over the weekend. Tony is also to document his work and research on the Javascript viewer.
 
Tony is at roadblock with the Javascript version of the Textual Viewer. It was agreed that we should start a retreat back to the PHP viewer and move forward from there. The discussion was left at Tony was going to think about it over the weekend. Tony is also to document his work and research on the Javascript viewer.
  
 
'''This week:'''
 
'''This week:'''
 +
 
Review updated milestones for Tony Le
 
Review updated milestones for Tony Le
 
Review updated milestones for Chris Sumption
 
Review updated milestones for Chris Sumption
Line 62: Line 64:
  
 
'''Notes:'''
 
'''Notes:'''
 +
 
Tony wants to proceed with adapting the PHP viewer so popovers can display dynamic content. We discussed what that would look like:
 
Tony wants to proceed with adapting the PHP viewer so popovers can display dynamic content. We discussed what that would look like:
 
Could write a Javascript application that gets called when the HTML page is completely loaded and the “onload” event is fired for the page.
 
Could write a Javascript application that gets called when the HTML page is completely loaded and the “onload” event is fired for the page.

Revision as of 16:44, 27 February 2015

EBA Documentation Meeting Agenda, Friday, February 27th, 2015

Time: 9:00am to 10:00am Place: UW Libraries, Research Commons, Green C Attendees: Sarah Ketchley, Chris Sumption

From last week:

Project Wiki: Sarah now has access, It is possible to style the wiki, but this is a low priority right now. Chris will transfer his abridged help page from his wikimedia site. Google Drive: does not let users transfer ownership of documents across domains. Sarah would like Google Doc about what tags are allowed. A bug list spreadsheet should be created to track any bugs that appear in any of the technologies. Sarah found a link to this project: http://mitford.pitt.edu/1820-03-20-WElford.html .

This week:

Omeka “Person” items should contain a field that directly maps to the XML “Person” tag’s “ref” attribute (eg Newberry_Mary). The standardized authority control for names is not going to have the diary names in their data store. We should stay away from generating “Magic Numbers” to keep track of people The XML files themselves do contain enough information to identify persons: The “ref” tag attribute if that’s not enough, the text contains temporal and spatial hints within the text (this “Mary Newberry” was in “Cairo” in “1912” - something along those lines. The bug list from the previous week was not discussed. How should the reader handle Person tags that have no Omeka information Should there be default content that the reader displays when there is no information for a particular person? Should an stubs be created in Omeka for every person listed in Volume 19? Can the XSLT sheet that generated the names list for volume 19 be modified to display how often names occur? Would that information be useful for deciding which names get researched first? Discussed FERPA and the projects documentation practices http://www2.ed.gov/policy/gen/guid/fpco/ferpa/index.html http://www.washington.edu/students/reg/ferpafac.html Omeka Webinar https://www.youtube.com/watch?v=sV9xcJMiZ8Y http://www.slideshare.net/jkmcgrath/hastac-scholars-omeka-and-digital-archives Future Webinars March 13, 3pm (EST): MIT Annotation Studio (Rachel Schnepper) April 15, 3pm (EST): Teaching and Researching with Scalar (Anne Cong-Huyen and Craig Dietrich) May 20, time TBA: Q&A with Omeka’s Outreach team May, date and time TBA: The Provoke Sound Project Student documentation requirements for future quarters, what does that look like? Is there a weekly due date? Can we access the students “world” knowledge (for instance 250 words per week, due on Fridays)?

Next week:

Documenting the meeting notes Versions from participants (Chris version, Sarah version)

Notes:

EBA Tech Meeting Agenda, Friday, February 27th, 2015

Time: 10:00am to 11:00am Place: UW Libraries, Research Commons, Green C Attendees: Sarah Ketchley, Chris Sumption, Tony Le

From last week:

Chris to create a 3 person JSON object, update all Volume 19 XML files to current version, update PHP Textual Viewer, copy Volume 1 from Allison’s branch and create its own development repository, and begin transfer of content from Wordpress to Omeka Tony is at roadblock with the Javascript version of the Textual Viewer. It was agreed that we should start a retreat back to the PHP viewer and move forward from there. The discussion was left at Tony was going to think about it over the weekend. Tony is also to document his work and research on the Javascript viewer.

This week:

Review updated milestones for Tony Le Review updated milestones for Chris Sumption Next Weeks Meeting Notifications (See Weekly Meeting Procedures)

Next week:

Notes:

Tony wants to proceed with adapting the PHP viewer so popovers can display dynamic content. We discussed what that would look like: Could write a Javascript application that gets called when the HTML page is completely loaded and the “onload” event is fired for the page. Could write a Javascript application that gets called on the “click” event for the “a” tag that anchors the popover. Could adapt the PHP script to dynamically generate the appropriate popover content upon creation of the “a” tag. It was decided to proceed with the third PHP option because that option makes the most sense. We are handling the content only once that way. We need to add the Omeka or correct spelling of the name of the person in the JSON list of person names. “sic” tag indicates a misspelling by either Emma B. Andrews or the typist. The Viewer will need to account for this at some point.