Date: Thu, 28 Mar 2024 14:55:58 -0400 (EDT)
Message-ID: <1469939230.28680.1711652158020@lyrasis1-roc-mp1>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_28679_1673506027.1711652158020"
------=_Part_28679_1673506027.1711652158020
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Agenda
Regular Items
- Instead of normal JIRA Review, today we'll review a few new 3.0 JIRA Su=
bmissions that have patches attached:=20
- DS-1127 - Submission improvements: document typ=
e-based submission (XMLUI only)
- DS-1223: Display frequencies of items in single=
browsing for selected indices (JSPUI only)
- DS-1224: Export items in various bibliographic =
formats (as RIS, BibTeX, EndNote, IEEE, ...) (JSPUI only)
- DS-1225: Show display values for controlled voc=
abularies in Item Page (JSPUI only)
- DS-1226: Batch import from basic bibliographic =
formats (Endnote, BibTex, RIS, TSV, CSV) (JSPUI only)
- DS-1227: Tag cloud for any browse index in the =
home page of DSpace (JSPUI only)
- DS-1228: Concatenate values of multi-value fiel=
ds in item display (JSPUI only)
Discussion Topics
- 3.0 Release - =
Reviewing larger features & planning the release?=20
- Advanced Embargo Pull Request: https://github.com/DS=
pace/DSpace/pull/43
- Other larger features listed as 3=
.0 tentative (esp. OAI 2.0, @mire features, CILEA features
- Are their particular features we want to schedule a special topic meeti=
ng around?
- Should we be finding ways to split up review of all the existing featur=
es on the 3.0 Release notes page (or "rank" which ones need many eyes versu=
s just a few)?
- Should we have someone(s) do a "quick scan" for open JIRA tickets with =
patches attached so that we can perhaps apply/review them for 3.0? (These c=
ould be "quick wins" as well)
- 3.0 Questions (from helix84):=20
- DS-531: ETD-MS schema out of the box. Again, the=
larger problem is that our =
metadata schema should be brought up-to-date with DCMI, but maybe we could =
tackle this smaller issue of ETDs. I suggest we add a "thesis" schema with =
5 fields mentioned in this table<=
/a> to support ETD-MS out-of-the-box. ~~helix84
- Need to review Gu=
idelines for Committing based on GitHub/Git?=20
- Thoughts on how we rework these polices to our new GitHub development e=
nvironment (with Pull Request policies, etc.)?
- Other topics?
Additional Ongoing Topics
- How can we "catch up" with JIRA Backlog?=20
- Do we need to "split up" the tickets & do quick reviews on our own?=
Or perhaps just split up tickets & do a very quick ranking & sched=
ule ones with patches for 3.0?
- Perhaps we schedule a "JIRA Backlog Bash" event (via IRC or similar) wh=
ere we work together to decrease the backlog over a few days or a week (thi=
nk of this like a "Test-a-thon" but instead we'd be working to just clear o=
ut the backlog as best we can).
- Brainstorming Features/Changes for 3.0. Can we work towards development=
teams around any of these projects?=20
- Larger DSpace projects which seem to have a lot of recent support:=20
- Moving towards a Common "Business Logic" / Business Services API. (I.e.=
avoiding duplication of business logic in all UIs)
- Metadata For All (i.e.=
metadata on all objects), SubTopic: Getting us up-to-date how we use Dubli=
n Core / DCMI. (Support from DCAT)
- AuthN & AuthZ issues, including: DS-994, DS-1006, DS-1007, DS-1088, and developer meeting on May 2, 2012
- Other DSpace projects receiving mention recently=20
Individual Status Updates=
If you have status items to report, please enter them below at least=
1 hour before the meeting starts.
Meeting Notes
Discussion of 3.0 Feature Submissions, build.properties discussion (DS-1=
208)
Meeting Transcript
Action Items
Action items coming out of this meeting go here, if any.
------=_Part_28679_1673506027.1711652158020--