Date: Thu, 28 Mar 2024 06:49:53 -0400 (EDT)
Message-ID: <1911213050.27432.1711622993358@lyrasis1-roc-mp1>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_27431_149045071.1711622993358"
------=_Part_27431_149045071.1711622993358
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
DevMtg 2013-11-06
DevMtg 2013-11-06
Agenda
Regular Items
"JIRA Backlog Hour" : Every We=
ds at 19:00UTC in #dspace IRC we will be working together to tackle our&nbs=
p;JIRA Backlog of=
"Received" tickets. This regular meeting will continue until we've bee=
n able to catch up on our backlog.
- Tim is unfortunately unavailable for JIRA Backlog Hour this week, but o=
thers are welcome to take part on your own.
Discussion Topics
- DSpace 4.0&nb=
sp;Status & Testathon progress=20
- Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
- What to do about the "./dspace index" scripts? Do we point=
them at Discovery now (the new default)? Do we leave them pointing a=
t Lucene?=20
- We already have one reported bug because of confusion about the "index"=
scripts no longer working "out-of-the-box" in 4.0: Unable to locate Jira server for this macro. =
It may be due to Application Link configuration.
- https://github.com/DSpace/DSpace/pull/379 : Wou=
ld this qualify as a 4.0 "bug fix" for Unable to locate Jira server for this macro. It may b=
e due to Application Link configuration. issue? This is anoth=
er request from Google to improve indexing in Google Scholar.
- Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
- Do we want to port to JSPUI?
- Other specific tickets to follow up on? Issues? Questions?
- DSpace 4.0 Tasks
- Search Interfaces (possibly standardizing on Discovery as the interface=
, with multiple providers)
- In DSpace 4.0, Discovery is enabled by default
- What do we want to do about plain-Lucene support?
- Option 1: Deprecate it in 4.0, and remove entirely in 5.0
- Option 2: Rewrite it so that it can be another provider behind Discover=
y (alongside Solr and possibly ES)
- For 5.0, we could also tentatively plan to release a Discovery on Elast=
ic Search option
Additional Ongoing Topics
- Brainstorming Features/Changes for future. Can we work towards developm=
ent teams around any of these projects?
- Larger DSpace projects which seem to have a lot of recent support:
- 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 =
Dublin Core / DCMI. (Support from DCAT)
- AuthN & AuthZ issues, including: DS-1566=
a> and developer meeting on Ma=
y 2, 2012
- Other DSpace projects receiving mention recently
Individual Status Updates=
If you have status items to report, please enter them below at least=
1 hour before the meeting starts.
Meeting Notes
Meeting Transcript
Action Items
(Action items go here, if any)
------=_Part_27431_149045071.1711622993358--