Versions Compared

Old Version 5

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version Current

changes.mady.by.user Grazia Quercia

Saved on

Key

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

...

  • (30 mins) General Discussion Topics
    1.  DSpace 7.6 release (final stages)
      1. Any final tasks to complete for the 7.6 release?
      2. Draft Release Notes begun at Release Notes#7.6ReleaseNotes
      3. Features needing basic Documentation in wiki:
        1. Batch Policy Management - Basic usage documentation - DONE: Bulk Access Management
        2. Signposting (how to enable/disable, basic configs. DONE: Signposting
        3. Browse Hierarchical Vocab? (Assigned to Atmire)
        4. Primary Bitstream? (Assigned to Atmire)
      4. Releases after 7.6:  Later releases will be bug-fix only.
        1. Tim will bring to Steering the suggestion to switch post-7.6 release numbering to 7.6.1, 7.6.2, 7.6.3 (for eventual bug fix release). This clarifies that 7.6 is the final feature release, and that every later release is a minor upgrade.
        2. Code review process brainstorms: See Incentivizing Code Reviews and PR Testing
    2. Google Scholar would like to perform a detailed indexing test on a single DSpace 7 production site. Looking for a volunteer (or two)?
      1. Goal is to find any obvious indexing issues in a "well configured" DSpace 7 site (if any).  Ideally this site would be running 7.5.
      2. One issue they are already aware of. Lack of 301 redirect for old URLs: https://github.com/DSpace/dspace-angular/issues/2265
    3. (No Updates) Demo Site migration to Lyrasis (https://demo7.dspace.org/ and https://api7.dspace.org/server/)  
      1. Exact date of switchover date to be announced. 
    4. 4Science proposed to present
      1. COAR Notify on July 13th 2023
      2. ORCID Login improvement on July 20th 2023
      3. Angular : library-based architecture proposal updated proposal on July 20th
    5. (Other topics?)
  • (30 mins) Planning for next week
    • Review the Backlog Board - Are there any tickets here stuck in the "Triage" column?  We'd like to keep this column as small as possible.
    • Review the 7.6 Project Board - Assign tickets to developers & assign PRs to reviewers.
      • Paid (by DSpace project) developers must keep in mind priority. If new "high" or "medium" priority tickets come in, developers should move effort off of "low" priority tasks.
      • Volunteer developers are allowed to work on tickets regardless of priority, but ideally will review code in priority order

...