Page tree
Skip to end of metadata
Go to start of metadata


This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to's the info:



  1. Report from Andrew Woods re: performance testing meeting

    1. Next meeting: 2015-11-09 Performance - Scale Meeting

  2. Report from Aaron Birkland re: API-X activity
    1. Next meeting: 2015-10-30 - Fedora API Extensions Meeting
  3. API specification: what triples are we committing to on which resources
    1. FCREPO-1765 - Getting issue details... STATUS
    2. FCREPO-1800 - Getting issue details... STATUS
    3. FCREPO-1715 - Getting issue details... STATUS
  4. Clustering activity and opportunities

  5. Review priority bugs below
  6. Close (or justify) old pull requests, especially those older than ~6 months
  7. ...

Ticket Summaries

  1. Please squash a bug!

     Click here to expand...

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due

  2. Tickets resolved this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution

  3. Tickets created this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution


1 ------ Report from Andrew Woods re: performance testing meeting

The initial conversation was focused on surfacing the salient requirements and concerns in the areas of performance and scalability. It was recognized that a reproducible benchmarking suite, collaboratively defined and agreed upon by the community, would serve the purpose of clarifying the current state of Fedora as well as identifying changes with subsequent Fedora releases.

The benchmarking items are being collected on the wiki ( You are encouraged to review and update the content of that page.

Additionally, Fedora performance testing has been executed and documented in the past. Links to this work are also referenced in the above wiki page. As a first step in designing a benchmarking approach, this prior art must be reviewed.

A scripted set of tests that runs over F4, and document in a systematic way over a set of community identified goals?
What are the benchmarks?
What are the tools?
Where we are lacking, adding tickets to make improvements.

Very large video files, and LDP interactions (Hydra) Questions where current LDP interactions can be improved on both client and server side.

Batch migration and ingests with fixity on the way in. Sharing of fixtures to have common tools.

Doron Shalvi has started to do some scalability testing on the migration front. Run into some OOM in migration-tools side, not on F4 side. Andrew Woods suggests what is most helpful is to create a Jira ticket with all relevant information so it can be properly addressed. Michael Durbin has been waiting for some real feedback before investing time. 

Discussion around knowledge of large scale migration tests in the community. 

Meetings every two weeks for performance and scalability. Next meeting on Monday Nov. 9, 2015 @ 1:00pm ET

2 ------ Report from Aaron Birkland re: API-X activity
Collected 30 use cases from various institutions. 
Agreed to move on to distilling requirements.
Criteria for evaluation agreed upon.
Started working through the evaluation of use cases.
Meeting tomorrow Friday Oct. 30, 2015 @ 2:00pm ET. Meeting bi-weekly.
Currently no formal roles or time commitments, are they ready to formalize.

The async storage effort had the idea to work with API-X effort. The use case from async storage will be sent to API-X to see which parts might or might not be applicable.
Some synergy between these two efforts.

Aaron Birkland is now working for Johns Hopkins. To be able to invest more time in the API-X architecture.

3 ------ API specification: what triples are we committing to on which resources
Fedora is moving toward a tightly specified API. One part is that when you make a request on a RDF source you get specific triples. However in some instances the triples returned are not always the expected or desired ones. This clean-up is part of moving Fedora towards a formalized API as one of our technical priorities
Better to have an assessment of the triples Fedora provides and their value to the community instead of a bunch of tickets singling out one or more problematic ones.
Esmé Cowles feels this is important and would like to help in the effort, I.e. to write up some of this specification.

A. Soroka - are we referring to the contents of the system managed triples "box". Those that are not defined by LDP, but extra triples defined by Fedora? We should be excluding from this talk the LDP defined triples and restrict ourselves only to the extra server-managed triples Fedora provides.

Aaron Birkland: What about optional LDP features that Fedora supports and the specific way in which Fedora supports them?
A. Soroka: This is specifically Fedora server managed triples. Or the reverse: is there any LDP defined triples the community can think of that should be part of this process?
Andrew Woods: I think the Fedora API is a contract between Fedora and it's community and what each expects to receive from the other.
A. Soroka: We as the Fedora community have no clear definition what system managed triples are and what their used for and therefor whether we need them. (ie. FCREPO-1765 - Getting issue details... STATUS  - rdf:type versus fedora:mixinTypes)

Strip unused triples and document any that will continue to be presented.

A. Soroka feels we will be on the prune side more than document side. Unknown User (daniel-dgi) agrees.

Is this a high-level ticket
A. Soroka feels that all triples that remain should be mapped to RDF. Unknown User (daniel-dgi) possibly dcterms??

Esmé Cowles and A. Soroka both volunteered for this effort.
One ticket to perform a review which will result in more tickets or subsuming some other tickets.
Related tickets:

Key Summary T Created Updated Due Assignee Reporter P Status Resolution


4 -------- Clustering activity and opportunities
avmich and p_ire are interested in clustering and are reaching out for assistance.
Are we reaching critical mass on a group that can help move clustering forward and improving our documentation.

Encouraging a more concerted effort around clustering.
Unknown User (daniel-dgi) is interested in joining the effort.

Should we try to get the community to articulate some specific goals/objectives around clustering in Fedora and provide a forum to work on these.

Should the first call out be to just figure out if there is a common understanding of what "clustering" means.
General Fedora configuration and scripts around the setup/testing of clustering would be available.
Unknown User (daniel-dgi) to make the call out on the fedora-tech list and initial wiki-page.

5 ------ Review priority bugs below

Some high priority bugs waiting for some one to pick them up.
Esmé Cowles feels FCREPO-1764 - Getting issue details... STATUS  is a high priority. Possibly tied to FCREPO-1801 - Getting issue details... STATUS .
A. Soroka The F4 reference implementation has an actual thing behind the hash uri.
There is a discussion to be had and is being had on e-mail list.


FCREPO-1800 - Getting issue details... STATUS  - Esmé Cowles feels this is straight up and plans move on it.
FCREPO-1803 - Getting issue details... STATUS  - follow-up to single subject work.
FCREPO-1753 - Getting issue details... STATUS  - is same as above
FCREPO-1799 - Getting issue details... STATUS  - Andrew Woods feels this is low-hanging

6 ----- Close (or justify) old pull requests, especially those older than ~6 months

Tabled to next meeting