Page History
...
(15 mins) Developer Stand Up - Developers give brief updates on their effort (or their team's effort).
- Update/see "Current Work" section below based on your status. Please feel free to update prior to meeting.
- Please highlight any new work (needing reviews/testing), any blockers (for you), and any discussion topics you may have.
- (25 30 mins) General Discussion Topics
- (20 mins) Next Steps on BTE transition to Live Import (based loosely on 2020-05-18 DSpace 7 Transition BTE to Live Import Mtg and 4Science proposal to improve authority support in DSpace7)
- 7.0beta3:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-4514 - 7.0beta3:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-4515 - 7.0beta5:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-4491 - 7.1 :
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-4516 - 7.1 :
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-4517
- 7.0beta3:
- (10 mins) Quick update on Controlled Vocabularies and Authority Control (Discussion may be held for following week)
- Proposal for addressing side effects:
- Proposal for addressing side effects: Controlled Vocabularies and Authority Control in DSpace 74Science proposal to improve authority support in DSpace7
- How to move forward on Controlled Vocabulary feature: https://github.com/DSpace/DSpace/pull/2743 Review the 4Science plan for the transition from BTE to live import: can it be approved? can work start / be scheduled over the next sprints?
- Prior discussion documented in Controlled Vocabularies and Authority Control in DSpace 7
- (20 mins) Next Steps on BTE transition to Live Import (based loosely on 2020-05-18 DSpace 7 Transition BTE to Live Import Mtg and 4Science proposal to improve authority support in DSpace7)
- Tabled Topics (will not be discussed this week, but possible for next week)
- Finalize / approve the initial list of all authorization features which we should implement for the /api/authz/features REST endpoint. This list of features should be limited to only features which are required to enable/disable User Interface functionality. (In other words, we can always add more features in the future. We just need to approve the list necessary for 7.0)
- Review current spreadsheet (from Andrea Bollini (4Science) ) : https://docs.google.com/spreadsheets/d/1182LcD_WqIZRbUGWpLtBw0aOMR9jhbOVB7GZqtTpR9A/edit?usp=sharing
- Art Lowel (Atmire) : I don't see any immediate issues with the current set of features, but I would prefer a consistent naming scheme. I'd use canDoSomething for everything
- Tim Donohue added possible renames of these features based on Art's idea (see cell comments in spreadsheet). I like the "can[DoSomething]" naming scheme as well.
- Review current spreadsheet (from Andrea Bollini (4Science) ) : https://docs.google.com/spreadsheets/d/1182LcD_WqIZRbUGWpLtBw0aOMR9jhbOVB7GZqtTpR9A/edit?usp=sharing
- Finalize / approve the initial list of all authorization features which we should implement for the /api/authz/features REST endpoint. This list of features should be limited to only features which are required to enable/disable User Interface functionality. (In other words, we can always add more features in the future. We just need to approve the list necessary for 7.0)
- Assigning PRs for Review
- (As necessary) claim tasks for next week from DSpace 7 Release Plan spreadsheet
...
Overview
Content Tools