Versions Compared

Old Version 6

changes.mady.by.user Danny Bernstein

Saved on

compared with

New Version Current

changes.mady.by.user Andrew Woods

Saved on

Key

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

...

  1. Danny Bernstein
  2. Jared Whiklo  
  3. Andrew Woods  (star)
  4. Ben Pennell  
  5. Ben Cail 
  6. David Wilcox 
  7. Thomas Bernhart (star)
  8. Daniel Lamb 
  9. Calvin Xu

Agenda

...

  1. In Review

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=13100
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  4. Tickets created this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Notes

Online User Group

  1. Can we, as the tech team, bring updates from the upcoming release?
    • Docker: logs, Fedora-via-docker
    • Fedora 6 features: search, OCFL
  2. Deadline: July 10th

July sprint

  1. July 6 - 10
  2. Objectives
    • Simple search
    • Clarity on F6 layout/headers
    • Side-loading API
    • Bug-fixing
    • Verify that jmeter testing works (large number of files, containers)
      • verify purpose? F6 improvements?
  3. DB issues
    • containment index with Postgres
    • search on MySQL
  4. Search issue
    • date filtering

Fedora ID limits

  1. Scope of discussion
    • encapsulation directory name (255 char limit)
    • path length: especially archival groups
    • Fedora-ID to OCFL-ID mapping
  2. Transparency of what is on the filesystem is very important
    • encapsulation dir: deriving path on disk is sufficient
    • files in object be named as provided
  3. Encoding for Windows may not be required on Linux

  4. From Slack

    No Format
    Some background on the various factors that impact what's allowed in a Fedora ID.
An ID part is a string that results from splitting an ID on the / character. For example: foo/bar/baz => [foo, bar, baz]
OCFL restrictions:
- ID parts cannot equal .
- ID parts cannot equal ..
- ID parts cannot be empty, eg. //
These restrictions are non-negotiable.

Fedora restrictions due to storage layout:
- ID parts cannot equal .fcrepo
- ID parts cannot equal fcr-root
- ID parts cannot equal fcr-container.nt
- IDs cannot end with ~fcr-desc or ~fcr-desc.nt
- IDs cannot end with ~fcr-acl or ~fcr-acl.nt
These restrictions are negotiable, but only by devising a different storage layout.

Filesystem restrictions:
- ID parts cannot exceed 255 characters
- IDs cannot contain characters that the filesystem considers illegal (this is a real problem for supporting Windows)
- The absolute path to a file cannot exceed 2048 characters (this is likely a squishy requirement on linux; on Windows the limit is ~32,767)
These restrictions vary by filesystem.

Filesystem restrictions can affect Fedora IDs in two ways.
1. Fedora IDs are mapped to OCFL IDs, and OCFL IDs are mapped to a path under the OCFL storage root. If all of these mappings are direct, then the Fedora ID determines the names of directories on disk.
2. Parts of Fedora IDs are used to name files within OCFL objects, OCFL logical paths, and these logical paths are mapped to content paths, which are the paths where files are physically stored on disk. Again, if all of these mappings are direct, then the Fedora ID determines the names of files on disk.

Database restrictions:
- IDs cannot exceed 503 characters
This restriction stems from the fact that Fedora IDs are used as keys for some tables, and 503 characters is the largest size these columns could be in MySQL. This restriction could be lifted if a surrogate key was used instead.

Search restrictions:
- IDs cannot contain: *, <, >, =
These restrictions are a result of how search conditions are parsed.
  5. Digital library system on Fedora 3 with VuFind front-end and custom backend. Stuck in holding pattern concerned with Fedora 4's persistence, happy with the direction of Fedora 6 and so trying out the migration-utils. Excited to have a roadmap to move forward. Full repository has about 600,000 objects, only done some small subsets for test migrations.
    1. Primarily (90%) images constructed into complex objects, but some other types in there as well.
    2. Desire a flat hierarchy with the RDF triples to maintain membership.
    3. Need some sort of Solr indexer to feed the Vufind front-end.
    4. Desire URIs to stay the same from the outer facing frontend, need to hang on to the PIDs.
  6. Fcrepo docker container for 5.1.0
    1. Simple search work is ready for more review.
  7. 5.1.1 Release - only one commit but seems easy enough to release. Discuss next week.
  8. Variety of issues still open and ready to be worked now or in the next sprint.
  9. Waiting for Peter Winckles
  10. Online Fedora User Group meeting, call for proposals is open.
  11. Demo server - Danny Bernstein  to check with Thomas Bernhart see about deploying from the new fcrepo-docker when new containers are built from new commits.

Actions
...