Versions Compared

Key

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

...

  • (BEFORE MEETING IN #dev-sprint) 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.
  • (20 15 mins) General Discussion Topics
    1. (DELAYED UNTIL JULY 30) Disabling some CLI flags in the Processes REST API for all scripts (e.g. `--eperson`), or supporting a way to configure some flags to be CLI-only.
      1. Some of these scripts have flags that we should never allow to be specified via the REST API (as they become a security issue when available on REST, but they are not a security issue via CLI). 
      2. See this initial issue around `metadata-import`
      Curation Tasks may need more discussion. A few flaws in current design
      1. REST PR: Output/Results is not being provided to the REST API.  This is different from DSpace 6 behavior.Repeats this security issue in REST APIhttps://github.com/DSpace/DSpace/issues/2822  We need to avoid allowing some CLI flags on REST API (e.g. `--eperson`) for all scripts.
      2. Angular PR: Currently in UI, tasks are runnable in two places...from the Curation Tasks page (which is easier to use) and from Processes UI.  Is there a way to hide them from the latter?
    2. OTHER TOPICS WELCOME: Send them before end of day on Tuesday, July 21
      1. The Curation Tasks PR has the same security issue, as it also allows the `--eperson` flag: https://github.com/DSpace/DSpace/pull/2820
      2. Another problematic flag is the ability to specify an output file location, e.g. in `metadata-export`: https://github.com/DSpace/DSpace/issues/2821
  • (45 (30 mins) Planning for next week

...

...