Committers Call 2014-02-24

Owned by Bill Branan
Jun 16, 2017
2 min read

Moderator: Adam Wead (Rockhall)

Notetaker: Carolyn Cole (PSU)

Attendees:

  • Jim Coble (Duke)
  • Lakeisha Robinson (Yale)
  • Drew Myers (WGBH)
  • Carolyn Cole (PSU)
  • Chris Colvard (Indiana)
  • Mike Stroming (Northwestern)
  • Edgar Garcia (Northwestern)
  • Michael Klein (NorthWestern)
  • Justin Coyne (DCE)
  • Glen Horton (Cincinnati)
  • Thomas Scherz (Cincinnati)
  • Adam Wead (RockHall)

  • Trey ? (Oregon Sate)

  •  

  1. Call for agenda items
  2. Proposal to release ActiveFedora 7 & Hydra Head 7
    1. Not going to include Oregon Digital RDF patch (because they don't have a cCLA). That can be 7.
    2. Anything holding up a release: No takers...
    3. RDF has only been unit tested. And Oregon does not have CLA 
    4. RDF patch breaks backward compatibility
      1. Oregon will write up the non-backward compatibility and send to hydra-tech
    5. Justin will Ship this week.
    6. Anything the Community can do?  Nothing off hand...

  3. ActiveFedora to_Solr issue with Sufia.  Is this more broad?
    1. When does this occur? When an object gets opened multiple times simultaneously (two users edit, background jobs, ect.)
    2. What happens now?  Fedora contains the entire metadata set.  Solr only contains the last metadata saved.  

    3. Not worth doing this at the Active Fedora since this is not a 100% sync.
    4. Not fixing the issue when you are holding it open for more time.
    5. Need to notify the user if you are going to lock the object that second user changes could be overridden
    6. Store a sequence on the solr record and then make sure the sequence number is 
    7. use AR to obtain a lock for the objects and create it and then release.
    8. Use a singe queue for doing all of you indexing, but you may still have stale stuff
    9. Solution may need to be at the implementor level.
    10. Mike Stroming (Northwestern) will create a gist to start the documentation process.
    11. Make people aware that this can be a problem and document possible solutions.

  4. Rails and Ruby Releases
    1. Ruby 2.1.1 was release today - Faster than 2.1.0
    2. Rails patches release last week 3.2.17 or 4.0.3
      1. non seem too serious
      2. Only includes a security fix
      3. Rails 4.1.0.rc is out.  Blacklight is not passing all of it's tests
        1. Any help from the community would be great
      4. Big changes between 2.0 and 2.1 is faster and bigger garbage collection

  5. Next Call: March 3rd
    • Moderator:  Michael Kleine
    • Note taker: Thomas Scherz