...
The Fedora community is working to establish a clearly defined specification for the core Fedora services [2]. This specification will detail the exact services and interactions required for a server implementation to be verified as "doing Fedora". A meeting was held [3] to discuss moving the versioning specification [4] forward as an implementation of the Memento protocol [5]. This proposal was met with agreement, so the draft specification will be has been moved into GitHub and then formatted using the W3C Respec tool [6] and published [7].
You are invited to comment on and contribute to the draft specifications [8].
Release Candidate Policy
In an effort to make the Fedora release process more consistent and predicatable, a new release candidate policy [9] has been established. In summary, the policy states that major and minor Fedora releases will have three weeks of public testing, whereas point or bug releases may have a shorter period. Additionally, the mailing lists that will be notified of the availability of release candidates are detailed.
Community-driven Activity
API Extension Architecture
The Sheridan Libraries at Johns Hopkins University was awarded an IMLS grant [] to support development on API-X through December, 2016. The deliverables include:
- Public release of the API-X architectures
- Associated documentation and dissemination
- Some common interest extensions
effort continues to move forward at a strong pace. At the last meeting [] it was decided that a list of tasks would be circulated to the group before being added to an issue tracker for resolution10] concrete plans to develop a number of extensions were discussed, including binary derivation and package ingest. Issues [11] in the GitHub tracker were assigned to be worked on over the next two weeks. If you are interested in the API Extension Architecture, please join the discussion on the fedora-community mailing list [12] and attend the next meeting on Thursday, May 12 at 1pm EDT.
Performance and Scalability
A number of test plans [] have been developed by the Performance and Scalability group, and some initial results are available. At the last meetingreport [13] was published in May to document the group made plans to document and run additional tests and work on profiling Fedora 4 [] using YourKit's work to date and future work. A number of test scenarios have already been run and the results are linked from the report.
If you are interested in Performance and Scalability, please join the discussion on the fedora-community mailing list [14] and attend the next meeting [15] on May 16 at 11am EDTJune 24.
Conferences and events
Upcoming Events
Open Repositories
Jisc/CNI Conference
Open Repositories [16] kicks off next month and there will be many Fedora-related workshops, presentations, and posters at the conference. We’ve counted 6 workshops, 35 presentations of various types, and 5 posters - you can find a complete list [17] on the wiki. We'll also be unveiling a new Fedora T-Shirt - be sure to grab one before we run out!
Islandora Camp BC
Islandora Camp [18] is returning to Vancouver for the second iCampBC, July 18 - 20. All West Coast Islandorians and anyone else who would like to see beautiful British Columbia while learning about Islandora are welcome to attend.
Previous Events
LPForum
David Wilcox, Fedora product manager will offer led a workshop entitled, Publishing Assets as Linked Data with Fedora 4 [1519] at the Library Publishing Forum [16] (LPForum 2016) to be held 20] held at the University of North Texas Libraries, Denton, Texas on May 18 from 1:00 PM-3:30 PM. All LPForum 2016 attendees are welcome—there is no need to pre-register for this introductory-level workshop.
TCDL
Andrew Woods, Fedora technical lead, will offer offered a Fedora 4 workshop [1721] at the Texas Conference on Digital Libraries [1822] (TCDL) on Tuesday, May 24 from 9:00 AM-12:00 PM. Space is limited to please register in advance [19].. The workshop was well-attended by participants who are currently using Fedora 4.
References
| No Format |
|---|
[1] https://jira.duraspace.org/issues/?filter=13122 [2] https://wiki.duraspace.org/display/FEDORAAPI/Fedora+Specification [3] https://wiki.duraspace.org/display/FF/2016-05-03+Fedora+Versioning+Review+Meeting [4] https://docs.google.com/document/d/1wpEVG3fNUYWNSmNdNIwTHEujhg-CAQf3hLKszfjpNO4 [5] http://mementoweb.org/guide/rfc/ [6] https://github.com/fcrepo/fcrepo-specification [7] http://fedora.info/spec/resource-versioning [8] https://wiki.duraspace.org/display/FEDORAAPI/Specification+Draft [9] https://wiki.duraspace.org/display/FF/Policy+-+Release+Candidates [10] https://wiki.duraspace.org/display/FF/2016-05-26+Fedora+API+Extensions+Meeting [11] https://github.com/fcrepo4-labs/fcrepo-api-x/issues [12] https://groups.google.com/forum/#!forum/fedora-community [13] https://wiki.duraspace.org/display/FF/2016-05+Performance+and+Scalability+Report [14] https://groups.google.com/forum/#!forum/fedora-community [15] https://wiki.duraspace.org/display/FF/2016-06-24+Performance+-+Scale+meeting [16] http://or2016.net/ [17] https://wiki.duraspace.org/display/FF/2016-06+Open+Repositories [18] http://islandora.ca/camps/bc2016 [19] http://www.librarypublishing.org/events/lpforum16/program/publishing-assets-fedora-4 [20] http://www.librarypublishing.org/events/lpforum16 [21] https://conferences.tdl.org/tcdl/index.php/TCDL/index/pages/view/2016-workshops [22] https://conferences.tdl.org/tcdl/index.php/TCDL/TCDL2016 |