Versions Compared

Old Version 5

changes.mady.by.user Andrew Woods

Saved on

compared with

New Version 6

changes.mady.by.user Andrew Woods

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attendees

Agenda

...

Agenda

  1. 20 - Review current fcrepo4 work.
    1. Triple store integration
    2. Customizable search indexes
    3. Large file performance
    4. Fcrepo3 migration
    5. roles-based AuthZ
  2. 10 - Scalability of the API for children
    1. Moving away from using Jena Model as container for triples in the kernel
    2. Moving to a streaming API all the way through the kernel
  3. 10 - Stakeholder needs in a customizable search indexer (Solr)
  4. 15 - Wiring and configuration (see also Comparison - Wiring

...

    • project descriptions in POMs (sufficient for dependency work)
    • pull request procedure
    • package level javadoc?
    • template project w/minimal POM dependencies for integration tests

...

  1. )

Previous Actions

...

Minutes

 

Agenda item: Fedora 3.7 update

Benjamin Armintor: 3.7 ready to release, but needs help on publishing documentation and webpage (Plone site ).

https://wiki.duraspace.org/display/FEDORA37/Fedora+3.7+Documentation

Benjamin Armintor: Reducing the number of sites to maintain ( wiki, sourceforge, etc )? Too many sites makes releases really painful.

General agreement to leave Fedora 3 documentation sources behind for Fedora 4

Greg Jansen: Use the github pages site?

Benjamin Armintor: performance related changes in 3.7.1 RC set for release this week

Benjamin Armintor and A. Soroka: possible future changes in FCREPO3 XML processing to allow for use of other JVMs than the Sun JDK.

Benjamin Armintor: Thoughts for improving memory use in F4 through the use of subclasses of ByteArrayInputStream and CharArrayWriter. Also, avoiding toByteArray() and other methods that require a full copy of data.

How to make sure people know to use these techniques?

Benjamin Armintor: Using the profiler showed excellent gains in memory efficiency with these techniques and other enhancements.

Agenda item: Code key signing 

Benjamin Armintor will start.

Agenda item: Fedora Four roadmap feedback

Committers and the institutions they represent should give feedback on that page.

Agenda item: Installfest

Greg Jansen: A way to get committers' a look to the current state,  as well as others.

Both physical and virtual settings for the installfest?

A. Soroka: Add to DLF page

Start thinking about creating introduction videos, especially configuration in different environments

Agenda item: Document practices

Need more than one line of description in POMs

Put pull request procedure in the top level readme and elsewhere

Package level JavaDocs in the kernel first, other places later

project descriptions in POMs

Ned to update top level POM ( assigning to Andrew )

benefit from good Maven metadata:  maven search engine results look better

examples of possible Maven archetypes: JMS driven, listening to internal event bus, Hello World, archetype

Agenda item: Wiring Practices

A. Soroka: https://wiki.duraspace.org/display/FF/Design+-+Wiring+and+configuration

Some comments have been added, looking for comments from people with Guice experience

Agenda item: Ideas for forthcoming sprint

Ye: In the next sprint, Search Function or MODS Sequencer

Clarifying features desired or needed

Thinking about the indexing of fields 

Differences between 3.x and FF views about metadata 

A. Soroka: Looking at the ModeShape XML sequencer is a good place to start to understand sequencers

Greg Jansen: Design pages as a place to get comments and feedback

The work of the sprint will be helpful for others to see 

Greg Jansen and A. Soroka: Differences between Fedora 3 object and Fedora 4 nodes

Greg Jansen: many sources of indexing information

A. Soroka: comparing JCR path languages and XPath

A. Soroka:  LDPath functionalities for resources created by Chris Beer: see fcrepo-transform module, also able to run SPAQL query against nodes

New item: Sprint info 

Greg Jansen: Two hour kickoff meeting on Monday at 11:00-1:00 EDT, six people on sprint

  1. reports on current work
    1. triple store integration  - Esme 
      1. will be looking at Mulgara and JMS indexer to incorporate non standard SPARQL queries
      2. looking at multiple levels based on reviewing use cases
      3. kitchen sink now has triple store  ( Question for Andrew:  Is vm built from master automagically )
        1. Answer from Andrew: "Yes, Jenkins deploys kitchen-sink on each commit to: http://futures6.fcrepo.org:8080/fcrepo/rest/"
    2. large file performance - Eric  
      1. 3 avenues explored
      2. researching different configuration settings ( e.g. caching hashes showed dramatic improvement )
      3. Scott commented on how fixity done in Fedora3
      4. fyi, looks like we actually read the data and do a new checksum when we do the fcr:fixity check, the low-level code that does the reading/checksumming is here:https://github.com/futures/fcrepo4/blob/master/fcrepo-kernel/src/main/java/org/fcrepo/kernel/utils/LowLevelCacheEntry.java#L92 (Esme)
    3. migration - Mike
      1. 90% completed and the remaining 10% is slow
      2. working on display, especially focused on performance when many children as displayed
    4. roles based - Greg
      1. will be working on integration test needed for effective roles for tree object
      2. roles can have expanded permission set ( Scott )
      3. XACML will be used for each role
      4. policy enforcement point
  2. API for children
    1. effective hierarchy needed to maintain good performance
    2. a couple of tests suggested  (Greg has the action items)
  3. search indexer - Markus
    1. external indexer (esp. Solr)
    2. Design - Customizable Search Index
    3. Scott described how they use Solr in F3.   change METS to Solr XSLT to customize
    4. what should be indexed?   data streams, text extraction from spreadsheet, PDF, etc.
    5. Possibly use METS which can point to binary files
    6. maybe use a default Solr schema; consider exposing to public and document how to use
    7. alternatives to XSLT should be considered
    8. need to keep the idea of distributed hardware ( e.g. separate Solr and Fedora)
  4. wiring - Adam
    1. changes will be hard and are hard now
    2. future proofing may not be as important as buy in from the group
    3. examples used currently or in the past: struts, Spring, JAX, CDI
    4. feedback from the community needed for https

...

    1. ://wiki.duraspace.org/display/FF/

...

    1. Comparison+

...

    1. -+

...

Actions

...

    1. Wiring
Actions