...
- Announcements:
- Tech team/committer profiles for upcoming newsletter
- Dan to OR next week
- OCFL Meet Up at OR
- Technology Info Session for F6 users last week
- Do we want a meeting next week? Dan will be at OR, Arran is out.
- Pop-up/Other Topics:
- Tombstone decision from Governance
- Would like to see more clear definitions outlined of PURGE vs DELETE
- Approve Jared's recommendations via this doc so long as the definitions of purge and delete are clear
- Paul Trilsbeek's ACL question/consideration from Slack (#Tech channel)
- "So Fedora has an internal mechanism for determining the effective ACL for a given resource, walking up the hierarchy if the resource itself doesn't have one. Would there be a way to get the effective ACL via the API? (with a single call, rather than probing and walking up the hierarchy until you encounter one)"
- Tombstone decision from Governance
Updates on:
- Open Tickets (but assigned in some cases):
Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3893 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3894 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3883 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3882 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3881 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3884 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3875
In Progress and older but still relevant open tickets:
Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3871 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3868
In Review:
Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3892
- isn't this one James said he would look at or that he sent notes to Dan about?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-3834
- Open Tickets (but assigned in some cases):
New tickets:
- Backlog Tickets to consider working: NA at present
- Next Meeting Chair:
- Chair: Jared Whiklo
- Note Taker: Demian Katz
- See Rotating Schedule here
Notes
- Announcements:
- Tech team/committer profiles for upcoming newsletter
- Dan to OR next week
- OCFL Meet Up at OR
- Technology Info Session for F6 users last week
- Jon Gostick from Cambridge setting up F6 from scratch. David Novak also on new F6 and brought up some new tickets
- Do we want a meeting next week? Dan will be at OR, Arran is out.
Next week cancelled. Demian happy to cary acrosss note taker
- Pop-up/Other Topics:
- Tombstone decision from Governance
- Would like to see more clear definitions outlined of PURGE vs DELETE
- Approve Jared's recommendations via this doc so long as the definitions of purge and delete are clear
- Paul Trilsbeek's ACL question/consideration from Slack (#Tech channel)
- "So Fedora has an internal mechanism for determining the effective ACL for a given resource, walking up the hierarchy if the resource itself doesn't have one. Would there be a way to get the effective ACL via the API? (with a single call, rather than probing and walking up the hierarchy until you encounter one)"
- Ben agrees it might be tricky
- "So Fedora has an internal mechanism for determining the effective ACL for a given resource, walking up the hierarchy if the resource itself doesn't have one. Would there be a way to get the effective ACL via the API? (with a single call, rather than probing and walking up the hierarchy until you encounter one)"
- Tombstone decision from Governance
Updates on:
- Open Tickets (but assigned in some cases):
in progress with BenJira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3893
403s on assets causing CSS ddisplay issuesJira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3894 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3883 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3882 Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3881
Arran has list of institutions who attended OAI-PMH sessions. Ping her when ready to testJira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3884
Ben thought this was done. will checkJira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3875
In Progress and older but still relevant open tickets:
Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3871
Dan using 11/17 in testing. at presentJira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3868
In Review:
Jira server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3892
- isn't this one James said he would look at or that he sent notes to Dan about? Yes it is.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-3834
- Open Tickets (but assigned in some cases):
New tickets:
- Backlog Tickets to consider working: NA at present
- Next Meeting Chair:
- Chair: Jared Whiklo
- Note Taker: Demian Katz
- See Rotating Schedule here