mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2025-01-27 05:49:12 +01:00
Add notes for 2020-10-07
This commit is contained in:
@ -23,7 +23,7 @@ During the FlywayDB migration I got an error:
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2020-10/" />
|
||||
<meta property="article:published_time" content="2020-10-06T16:55:54+03:00" />
|
||||
<meta property="article:modified_time" content="2020-10-06T23:38:45+03:00" />
|
||||
<meta property="article:modified_time" content="2020-10-07T14:44:39+03:00" />
|
||||
|
||||
<meta name="twitter:card" content="summary"/>
|
||||
<meta name="twitter:title" content="October, 2020"/>
|
||||
@ -41,7 +41,7 @@ During the FlywayDB migration I got an error:
|
||||
|
||||
|
||||
"/>
|
||||
<meta name="generator" content="Hugo 0.75.1" />
|
||||
<meta name="generator" content="Hugo 0.76.2" />
|
||||
|
||||
|
||||
|
||||
@ -51,9 +51,9 @@ During the FlywayDB migration I got an error:
|
||||
"@type": "BlogPosting",
|
||||
"headline": "October, 2020",
|
||||
"url": "https://alanorth.github.io/cgspace-notes/2020-10/",
|
||||
"wordCount": "956",
|
||||
"wordCount": "1077",
|
||||
"datePublished": "2020-10-06T16:55:54+03:00",
|
||||
"dateModified": "2020-10-06T23:38:45+03:00",
|
||||
"dateModified": "2020-10-07T14:44:39+03:00",
|
||||
"author": {
|
||||
"@type": "Person",
|
||||
"name": "Alan Orth"
|
||||
@ -317,6 +317,39 @@ $ http https://dspacetest.cgiar.org/rest/status Cookie:JSESSIONID=EABAC9EFF94202
|
||||
<li>We are curious to see if he gets a UUID when posting from MEL</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>I did some tests by adding his account to certain workflow steps and trying to POST the item</li>
|
||||
<li>Member of collection “Submitters” step:
|
||||
<ul>
|
||||
<li>HTTP Status 401 – Unauthorized</li>
|
||||
<li>The request has not been applied because it lacks valid authentication credentials for the target resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Member of collection “Accept/Reject” step:
|
||||
<ul>
|
||||
<li>Same error…</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Member of collection “Accept/Reject/Edit Metadata” step:
|
||||
<ul>
|
||||
<li>Same error…</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Member of collection Administrators with no other workflow steps…:
|
||||
<ul>
|
||||
<li>Posts straight to archive</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Member of collection Administrators with empty “Accept/Reject/Edit Metadata” step:
|
||||
<ul>
|
||||
<li>Posts straight to archive</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Member of collection Administrators with populated “Accept/Reject/Edit Metadata” step:
|
||||
<ul>
|
||||
<li>Does <em>not</em> post straight to archive, goes to workflow</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>Note that community administrators have no role in item submission other than being able to create/manage collection groups</li>
|
||||
</ul>
|
||||
<!-- raw HTML omitted -->
|
||||
|
||||
|
Reference in New Issue
Block a user