...
- Announcements:
- Arran to TCDL next week
- Will be meeting at the end of this month with the team from TACC re: an NSF Eager Grant to do large scale testing of F6 + their infrastructure set up
- Technology Info sessions next week (May 17th & 19th) - Sign Up to Participate
- OCFL Community Meeting Recap
- Pop-up/Other Topics:
- Slack Topic from Raphaëlle Lapôtre - Linked data notification in Fedora (https://fedora-project.slack.com/archives/C0F71T4E9/p1683706708248049)
- Islandora Slack question about admin permissions (https://islandora.slack.com/archives/CM5PPAV28/p1683572492855879) - Maybe this truly does need to be answered by Islandora community as I'm not sure where those permission settings would lie
- user says their Islandora gives fedoraadmin role same permissions as the administrator but would like to see more restricted roles for some users
- want to know what permission are essential for the fedoraadmin role b/c was hoping to be able to give a user access to add content, but not do everything
- Migration Updates:
Updates on:
- Open Tickets (but assigned in some cases):
Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3888 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3879
In Progress and older but still relevant open tickets:
- https://fedora-repository.atlassian.net/jira/software/c/projects/FCREPO/issues/FCREPO-3884
Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3840
In Review:
Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3891 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3890 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3879 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3878
- Open Tickets (but assigned in some cases):
New tickets:
- Backlog Tickets to consider working: NA at present
- Next Meeting Chair:
- Chair: Demian Katz
- Note Taker: Jared Whiklo
- See Rotating Schedule here
Notes
- Announcements:
- Arran to TCDL next week
- Will be meeting at the end of this month with the team from TACC re: an NSF Eager Grant to do large scale testing of F6 + their infrastructure set up
- Can use funding to solve / execute tech issue
- Focus on large quantities of data, supercomputing. If successful, will roll out broadly to UT-Austin.
- Technology Info sessions next week (May 17th & 19th) - Sign Up to Participate
- OCFL Community Meeting Recap
- Fedora heavily represented
- Raised issue of scale, number of files, several people agreed in chat. Known issue. May be investigated in OCFL v 2.
- Stefano Cossu looking to organize OCFL meetup at OR.
- Pop-up/Other Topics:
- Slack Topic from Raphaëlle Lapôtre - Linked data notification in Fedora (https://fedora-project.slack.com/archives/C0F71T4E9/p1683706708248049)
- Should be a lot of COR representatives at OR to discuss
- Linked data notifications are permanent - need to persist?
- Harvard - add to MSpace, get Dataverse ID
- Islandora Slack question about admin permissions (https://islandora.slack.com/archives/CM5PPAV28/p1683572492855879) - Maybe this truly does need to be answered by Islandora community as I'm not sure where those permission settings would lie
- user says their Islandora gives fedoraadmin role same permissions as the administrator but would like to see more restricted roles for some users
- want to know what permission are essential for the fedoraadmin role b/c was hoping to be able to give a user access to add content, but not do everything
- Looking for assistance for others to look at performance issue, which metrics would be helpful. May be config issue on Grafana.
- Villanova fixity situation
- Hoping to use AWS File Gateway to store files in S3 while looking like a local filesystem
- How to do fixity without having to download from s3?
- Thought they could do fixity in s3, which uses SHA-256. However, OCFL uses SHA-512.
- Perhaps Fedora use of OCFL should default to SHA-256 to be more compatible with S3, improve performance.
- Can add SHA-256 to Fedora objects, but would add work. Would prefer not to download objects from AWS.
- Slack Topic from Raphaëlle Lapôtre - Linked data notification in Fedora (https://fedora-project.slack.com/archives/C0F71T4E9/p1683706708248049)
- Migration Updates:
- U Manitoba - starting to consider test repos for migration
Updates on:
- Open Tickets (but assigned in some cases):
- Jared offered to takeJira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3888
- now has an PRJira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3879
In Progress and older but still relevant open tickets:
- https://fedora-repository.atlassian.net/jira/software/c/projects/FCREPO/issues/FCREPO-3884 - OAI-PMH epic. Dan started to flesh out subtasks in epic.
- banner work in progressJira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3840
In Review:
- update AWS deployer for Terraform - Dan created to build demo containers for OR meeting. Just needs some updatesJira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3891
- Add Fedora version info to http readable location - Dan added comment, should we always return HTTP 200 or sometimes an error? Mike also will look into, has some thoughts.Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3890
- see aboveJira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3879
- has open PR, updates to PR requested and addressed. Mike to re-reviewJira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3878 - PR for 3849, 3850 - Docker - Thomas to review, can probably be streamlined. Looking for a second independent reviewer. Dan volunteers.
- Open Tickets (but assigned in some cases):
New tickets:
- Backlog Tickets to consider working: NA at present
- Next Meeting Chair:
- Chair: Demian Katz
- Note Taker: Jared Whiklo
- See Rotating Schedule here