Midwest Fedora User Group Meeting. A place to meet in person to discuss topics, share experience and learn about Fedora, Hydra, Islandora, PCDM and other such fun things. 


This event is free and open to all who want to participate. Fedora veterans and newcomers, enthusiasts and curious technologists from the Library, Archive and Museum community are welcome.

Note: registration is required. Register here.


February 28th–March 1st, 2017

Day 1: 9:00am - 5pm  

Day 2: 9:00am - 3pm  

Start and end times are subject to change depending on schedule. See Agenda below.


The Art Institute of Chicago, Chicago, IL

The meetings will be held in two locations:

  • Operation Conference Room (OCR), within the offices area; 4K screen with attached Mac workstation + HDMI (and VGA?) connection for laptops, Ethernet + WiFi
  • Morton Auditorium (MA) in the museum; projector on stage, VGA (?) BYO laptop, Ethernet + WiFi


If you are coming from O'Hare airport the fastest and most convenient way to get to the museum is taking the Blue Line train to the Monroe stop and walk two blocks east on Monroe Street.

Driving directions, parking and other information are found on http://www.artic.edu/visit/directions-and-parking

Enter through staff entrance before 10:30am. Participants will be escorted through the staff entrance.

The staff entrance is on 125 East Monroe Street. Walk on Monroe past Michigan Avenue and proceed for a few hundred feet and you will see a big loading dock on the right side, just before the train tracks. The staff entrance is a white door to the right of the dock. 

If you are joining after 10:30 you can enter directly through the Michigan Avenue entrance of the museum. Email Stefano Cossu (scossu at artic period edu) to get in. 


A list of attendees will be published following the event.


Sign up for sessions using the registration form

Day 1: Presentations

9:00-10:30Welcome and discussionOCRAll Present yourself and your institution, and share brief thoughts and experience about your Fedora implementation or plans.
10:30-11:30Coffee break, discussion and transfer to Auditorium   
11:45-12:30pmFedora updates and Q&AMAAndrew Woods (Duraspace)
12:30-1:30LunchMuseum cafe

1:30-2:00AIC UpdatesMAStefano Cossu, Kevin Ford (AIC) Latest on LAKE, the AIC's Fedora/Hydra Digital Asset Management System
2:00-2:30Fedora at ICPSRMAHarsha Ummerpillai (ICPSR)Archonnex@ICPSR, Fedora Admin GUI using ReactJS & JEE.
2:30-3:00Open Science FrameworkMARick Johnson (ND)Overview of Fedora and Open Science Framework integration efforts at Notre Dame, Johns Hopkins, and Center for Open Science
3:00-4:00Discussion and wrap-upMA  
6:30Drinks & Dinner   See dining below

Day 2: In-depth discussion

 9:30-10:30Gather use cases for direct query featureOCR
10:30-12:00pmFedora code walk-throughOCR
1:00-1:45API-X demo
 1:45-2:30Content modeling
2:30-3:00Fedora documentation

Minutes from discussions

 I -- Specific searches people might like to have exposed in Fedora

Traversing a graph -- getting stuff that's one step away from a resource. This sounds like a sparql query -- two use cases, one based on path, and the other based on date or date range, and response is always a list of uris

Give me all the children of a resource where x property matches in one way or another y value.

Give me all children underneath a resource .. as well as 404 or 405s or 410s, information on the lost resources.

Let me filter the attributes returned. A search returns hundreds but we're only interested in a few. No, clients can't define set of attributes you get back (server attributes and user attributes, clients can specify that they do not want server attributes, but can't manage either list of attributes).

We'd like some very basic counts of things: how many resources are in Fedora in order to compare with what's in the triple store or solr -- we don't have a way to get that, and Fedora is the canonical resource
We'd like quick snapshots of how many binaries vs non-binaries in the repo, the size of binaries .. how many of each RDF type, how many are there in general, etc.. You can do this with LDPath but that will hit every resource, which is a memory hit and not really what is needed.


(There is a youtube video - marketing-focused; how requests are intercepted, two models for doing so).
On the gihub repo there are dockr containers and steps for getting it up and running and providing feedback.

APIX is an interface to Fedora, with methods for lots of things apps commonly want to do (processing of binaries with ImageMagick or FITS). Apps talk to APIX and it does one of two things: passes data to a service to do something, then puts data in Fedora and then sends back response, or puts something into Fedora and then passes something off to a service and then sends response.

III -- ACLs ... many get created, but does community know much about how and what implications are?

IV -- PCDM. UI might be bigger priority than community collectively realizes.

V -- Jersey is the language Fedora uses to manage REST .. Jersey is an implementation of the JAXRS specification.

VI -- Code walkthrough
  Main entry point is Fedora LDP -- there's an http module that is accessed by clients 

Other Information


Fancy hotels near the museum:

Palmer House (Hilton)

Silversmith Hotel

Best value: Club Quarters a few blocks away


GePaDe – my favorite breakfast and lunch place, across the museum entrance. You must try their cannoli and gelato. They serve pizza too.

Museum Cafe – the AIC lower level cafe offers healthy, tasty and convenient lunch options. Can get crowded in the summer.

Vapiano – across the Palmer House. Good pizza & pasta