Another option for an easier(?) way to  run Fedora 4 is with this Docker image: https://registry.hub.docker.com/u/jermnelson/semantic-server-core/. You still have to manually start-up tomcat but then you can connect to a Fedora 4 instance running on port 8080 on your Docker host.

This and related images are in active development and debugging so let me know of any problems or questions.

Thanks,
Jeremy Nelson
Metadata and Systems Librarian
Colorado College

-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Esmé Cowles
Sent: Wednesday, July 08, 2015 2:28 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] Fedora 4 repositories with open API?

And if there aren't any open Fedora 4 repositories forthcoming, you can always use fcrepo4-vagrant to spin up your own pretty easily:

https://github.com/fcrepo4-labs/fcrepo4-vagrant

-Esme

> On 07/08/15, at 4:01 PM, Tom Cramer <[log in to unmask]> wrote:
> 
> Hi Patrick,
> 
> To my knowledge, Penn State has one of the current Fedora 4 repositories in production; a few others are close (including the Royal Library of Denmark). You might also want to post th is query on the [log in to unmask] and/or [log in to unmask] list.
> 
> Hope this helps, 
> 
> - Tom
> 
> PS. Has there been any thought that Omeka S might also be IIIF-friendly <http://iiif.io/>, and able to present image-based resources from any IIIF-compatible repository by consuming both the IIIF image and presentation APIs <http://iiif.io/technical-details.html>? I can muster up some live IIIF API endpoints, if you are interested. 
> 
> 
> 
> 
> 
>> On Jul 8, 2015, at 9:07 AM, Patrick Murray-John <[log in to unmask]> wrote:
>> 
>> Hi all,
>> 
>> The Omeka <http://omeka.org> web publication tool for GLAMs is working on a new version, Omeka S, that will include modules for connecting to various other systems, including Fedora 4.
>> 
>> Does anyone have a Fedora 4 installation with open API that we could use to test the basic reading and import mechanisms against? This would be for development and testing purposes only.
>> 
>> Many thanks,
>> 
>> Patrick Murray-John
>> Omeka Director of Developer Outreach