The Fedora Project is pleased to announce that the West Coast Fedora Camp, hosted by the Caltech Library, will be offered at the California Institute of Technology's Keck Institute for Space Studies in Pasadena April 11-13, 2016.
Fedora 4, the new, revitalized version of Fedora, was released into production in November 2014. Fedora 4 features include vast improvements in scalability, linked data capabilities, research data support, modularity, ease of use and more. Fedora Camp offers everyone a chance to dive in and learn all about Fedora 4.
Training will begin with the basics and build toward more advanced concepts–no prior Fedora 4 experience is required. Participants can expect to come away with a deep dive Fedora 4 learning experience coupled with multiple opportunities for applying hands-on techniques working with experienced trainers and Fedora gurus.
This West Coast Fedora Camp at Caltech is based on the inaugural Fedora Camp that was held at Duke University in November ("Letter From Fedora Camp"). 40 participants shared ideas and worked together to better understand how to take advantage of the Fedora open source repository platform. The curriculum led the group through in-depth technical “deep dive” sessions as well as question and answer discussions regarding features, migrations, data modeling, indexing for search and discovery, extending Fedora, and more. The attendees' feedback was very positive, and the organizers have used their input to enhance the camp experience for developers and administrators alike.
Register here. Attendance is limited to the first 40 registrants. Payment is due upon registration. While an invoice option is available, please note that the invoice must be paid within 30 days of receipt or registration will be canceled. Local accommodations are available at a reduced rate.
Cancellations must be made by March 11, 2016 to receive a refund (minus a $35 administrative fee). Cancellations after this date will not be eligible to receive a refund. Contact David Wilcox <firstname.lastname@example.org> with questions.