Date: Thu, 28 Mar 2024 05:49:00 -0400 (EDT) Message-ID: <518653114.27348.1711619340543@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_27347_176371902.1711619340543" ------=_Part_27347_176371902.1711619340543 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This is the April 2017 edition of the Fedora Newsletter. This ne= wsletter summarizes the most significant activities within the Fedora commu= nity over the last month.
Fedora is designed, built, used, and supported by the community. An easy= and important way that you can contribute to the effort is by helping reso= lve outstanding bugs. If you have an interest in gaining a better understan= ding of the Fedora code base, or a specific interest in any of these bugs, please add a comment to a ticket and we can= work together to move your interest forward.
Earlier this month, two common Java library vulnerabilities surfaced:
Although related libraries have historically been included in Fedora's d= eployable artifacts, investigation confirmed that Fedora is not subject to = the vulnerability; in fact, Fedora is not actually making use of the affect= ed libraries. Because of this, and to eliminate any doubt of a potential vu= lnerability, the libraries have been removed from the codebase and a patch = release has been issued to the 4.7 line and backported to the 4.6 line.
Release notes for Fedora 4.6.2 and 4.7.2<= /a> are available on the wiki.
The Fedora community is working to establish a clearly defined specifica= tion for the core Fedora services. This specification details the exact ser= vices and interactions required for a server implementation to be verified = as "doing Fedora".
Community members raised issues around implementing Batch Atomic Operati= ons in a distributed architecture, leading to a decision to separate this e= lement into its own specificatio= n document. We are also seeking further input on supporting different k= inds of external content.
The draft specification has been published and is looking for com= munity comments. Following this round of input, we plan on an initial relea= se of the specification in the spring of 2017.
As the formalization of the Fedora API Specification matures,= it will be increasingly important for existing applications and frameworks= over Fedora to adjust client/server interactions to the specification. The= services defined in the Fedora API Specification are the same ones that ar= e currently provided by Fedora 4, but the interaction models in some cases = are changing to be more in line with broader standards. The effort of this = group is to facilitate the adjustment of client-side tooling by detailing t= he "deltas" between the current Fedora 4 implementation and the emerging sp= ecification.
Please stay tuned for updates and opportunities for engagement.
The Fedora project relies on many individuals and institutions to ensure= the project's success. We are grateful for their commitment and will showc= ase their contributions in a series of community profiles aimed at recogniz= ing our contributors=E2=80=99 achievements, and introducing them to the res= t of the community. The first article in the Fedora Repository Contributor = Profile series features Danny Bernstein, who has a long history with DuraSp= ace technologies and is a new contributor to the Fedora repository team. Hi= s focus is on core Fedora performance issues particularly as they relate to= development of the new Hyku repository. The full article can be found= on the DuraSpace website.
One of the design goals of Fedora is to simplify the process of both get= ting your resources into and out of Fedora in a standardized way. This enab= les the reuse of Fedora resources in other contexts, such as exporting to a= separate preservation system, as well as provides a pathway for migrating = across Fedora installations. This design goal is being met by an external import/export tool that supports t= ransacting in RDF and (optionally) BagIt bags.
We will be organizing another code sprint to address phase 3 requirement= s in the near future. If you would like to participate as developer, te= ster, or to write documentation, please contact Andrew Woods.
The Performance and Scale group met on March 20 and discussed progress on the "many members" perfo= rmance issue, which affects retrieval times for resources with a large = number of members. Danny Bernstein pursued a number of optimization strateg= ies and found that a combination of parallel processing streams and increas= ing the size of the ModeShape cache produced significant performance gains = of 5-8x.
In an attempt to simplify the task of keeping up with Fedora-related mee= tings and events, a Fedora calendar is available to the community as HTML and iCal .
The CNI Spring mem= bership meeting will take place April 3-4 in Albuquerque, NM. The = meeting will feature project briefings and panel discussions, and will be i= mmediately followed by the annual DuraSpace Summit on April 4-5. The state = of DuraSpace will be presented highlighting 2016 successes, ideas for new s= trategic directions, and open source project updates. In addition to the op= portunity for small and large group discussions, each project will hold the= ir own meeting, as organized by the respective Project Steering Groups, to = discuss projects' goals, objectives, and resources for 2017.
The annual Innovative Library in Digital Era con= ference will take place April 3-5 in Jasn=C3=A1, Slovakia. The ai= m of the conference is to present visionary and original ideas based on the= extensive experience of the participating experts and institutions. This y= ear's agenda will fe= ature a number of sessions on research data management, including a present= ation on stewarding research data with Fedora by David Wilcox.
The 9th RDA Plenary = Meeting will take place April 5-7 in Barcelona, Spain. The plenary will= feature interest and working group sessions on a number of topics related = to repositories and Fedora, including the Research Data Repository Intero= perability working group, and the Libraries for Research Data, Long Tail of Research Data, and Repository = Platforms for Research Data interest groups.
The next Hyd= ra Camp will take place April 17-20 at Emory University in Atlanta, GA.= Led by Data Curation Experts, Hydra Camp is open to all dev= elopers interested in building skills working with the Hydra technology fra= mework. Please = register in advance to attend.
Museums and the Web will be hosted in Cleveland, OH from April 19-2= 2. The conference features advanced research and exemplary application= s of digital practice for cultural, natural and scientific heritage. This y= ear's conference includes a workshop on Hydra-in-a-box for museums led by Davi= d Wilcox and Stefano Cossu. Workshop seats are limited so please register in advance.
From printed newspapers to born-digital news, libraries and other cultur= al heritage institutions have a central role in ensuring future access to n= ews content. The IFLA News Media Conference, which takes place April 27-28 = in Reykjav=C3=ADk, Iceland, will examine issues and challenges in coll= ecting and preserving the news and making it available to users. The confer= ence will include a Fedora workshop delivered by D= avid Wilcox.
Data Curation Experts is offering an Avanced Hydra Camp on May 8-10 in M= inneapolis, MN. This camp is for developers with a year or more hands-= on Hydra development experience who have already attended Hydra Camp or hav= e equivalent knowledge. Please register in advance to attend.
The second Islandoracon will be held in Hamilton,= Ontario from May 15 - 19, 2017. The conference= schedule will take place over five days, including a day of post-confe= rence sessions and a full-day Hackfest. Please reg= ister in advance to attend.