DCAT met and talked about / approved DOI field standardization in DSpac=
e 7: Unable to lo=
cate Jira server for this macro. It may be due to Application Link configur=
ation. Work is looking for a volunteer, but may fall t=
o a Committer who is interested in chipping in.
Lotte has made a little progress on truncation, but has still spent mos=
t of her week working on other projects, so no PR yet.
I=E2=80=99ve made some progress on the POST support, we discussed last =
time about how to refactor the request store, using hashes or UUIDs. I went=
with UUIDs, for the sake of performance, and refactored the request store =
to work with them, and created an index to find the UUID of get request bas=
ed on their URL. Still to do: keep POST responses out of the response cache=
, and write tests. A WIP branch can be found here: https://github.com/DSpace/dspace-ang=
ular/compare/master...artlowel:post-support
Andrea Bollini (4Science) notes that 4S=
cience has implemented POST requests (and DELETE and PATCH) in the in-progr=
ess Submission UI efforts
ACTION:=
Giuseppe Digilio (4Science) will create a ticket in 'dspace-angular' ar=
ound supporting new request types, and link Art Lowel (Atmire) to the in-progress code. That way we can e=
nsure these two efforts are synchronized and can be merged together.
Tim has updated/enhanced the Workshop proposals with the details requir=
ed for submission. Andrea & Art should review these updates
Tim will also add in a proposal for the DSpace 7 Update talk prior to l=
eaving for holiday. Will likely submit this talk in early January upon retu=
rning
Tim also volunteered to support both workshops, if needed. Willing to b=
e a second person / give an intro talk (as needed), and generally help howe=
ver needed.
ACTION: Submit all of these proposals. Andrea Bollini (4Science) and Art Lowel (Atmire) can feel free to submit proposal b=
efore holidays, as they see fit (Submitted proposals can be updated=
prior to the deadline). =
Tim Donohue will submit the Talk proposal in early January, and will ch=
eck in after holidays to submit anything that has not yet been submitted.=
li>
Andrea notes he's still not sure that this endpoint needs =
to support general user requests. General users (non-admins)=
can receive an access-aware list of items/bitstreams via the existing Brow=
se/Search endpoints. Do we need another endpoint that supports this s=
ame concept? Or can we use the existing Browse/Search endpoints to allow ge=
neral users to find items accessible to them? However, that sai=
d, administrative users may need to be able to get a =
full list of all items in the system (for various admin tasks). Could=
we simply limit access this access to Admins?
Tim sees the point. Will add more comments to the PR to summarize and s=
ee if there are use cases we are missing in this discussion.
Work-in-progress PR could use early feedback (especially a code revi=
ew). Andrea worries this will only get bigger. Currently Integr=
ation tests are missing, but will be built out in near future to "prove" ou=
t the code
Discussion of how best to get this merged / moved along ASAP
Best to get this existing functional "finalized" by the end of the year=
(with integration tests) or early January. Keep any other features for fut=
ure PRs. Let's get this one cleaned up, add integration tests, and get merg=
ed.
ACTION: In first January meeting, we will do an in dep=
th look of this PR, and merge it in the first week or two we are back.
ACTION: Mark H. Wood =
will also start to review the documentation at Configuration changes =
in the submission process , and provide feedback from the point of=
view of a new set of eyes. These configuration changes drive all the=
new submission functionality in the PR.
Giuseppe gave us a live demo (via screen sharing) of the latest Submiss=
ion UI code.
Functionality is looking GREAT! Tim and Mark both impressed
There are a few submission panel types that are missing (CC Licensing, =
Access control panel, etc). However, we recommend submitting a PR soo=
n with the existing functionality, and leave those ot=
her panel types for future PRs.
ACTION:Giuseppe Digilio (4Science) will create an early PR of this work b=
efore the end of the year. It likely will not include unit tests (those wil=
l come in January). But, it will provide an opportunity for others to revie=
w and test the current work.
ACTION: When we return in January, we will make i=
t a priority to get this work (and the backend work, see PR 1889 above) sta=
bilized and merged ASAP (future panels and/or enhancements can come i=
n future PRs). It'd be great to be able to do a video demo of this fu=
nctionality for our community in late January or early February, if possibl=
e.
Next Meeting will be Thurs, Jan 11 at 15:00UTC via Google Hango=
uts