Time/Place

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

Attendees 

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

Agenda

  1. Announcements/Updates
    1. Tickets fixed last week:
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Fedora Online User Group (Week of August 10)
    3. Ongoing sprints
  2. July Sprint 
  3. Defining Fedora ID limits
    1. What are limits are non-negotiable
    2. Of those that are negotiable, what is the recommendation
      1. is it user friendly?
      2. will it be performant?
      3. will anyone be unable to use Fedora as a result?
    3. List of limits to consider:
      1. OCFL object root directories
      2. uri limits
      3. invalid characters or character patterns
      4. ?
  4. Current work
    1. https://github.com/fcrepo4-labs/fcrepo-docker 
    2. https://github.com/fcrepo4/fcrepo4/pull/1707
    3. Other work?
  5. 5.1.1 Release? 

    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  6. We should submit some proposals to the "Online Fedora Users Group"
    1. Submission form
  7. FCREPO-3306 - Re-establish Demo Server OPEN  - what are the dependencies?
  8. Remove `master` branch?

  9. Your Topic Here

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Tickets

  1. In Review

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  4. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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

    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.

Actions




  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.