<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
<p>Hi Martin,</p>
<p>There is no facility to give temporary permission to edit an
item, it fact there is not way to allow the user to edit a
particular eprint record and no others, especially so if the item
is already live. I would be worried how you would ensure
oversight of these records that users got temporary permission to
edit. As if the item was already live a malicious user could do
quite a bit of damage.<br>
</p>
<p>A not fully thought out solution might be to have a form that
allows a user to submit a specific item change request. This
change could then simply be approved by an editor/admin that would
then cause the eprint record to be updated. As your use case is
just for a single field, it is probably easiest to build a plugin
that focusses on just that field and allows you to only submit
additive changes for it. This would require its own "eprint
change request" data object, to send to editors/admins for
approval, a bit like the current review queue.<br>
</p>
<p>Thinking about this more generically, having an eprint change
request form that can be used by registered users to submit a
change request to add/remove/modify any field on any item may be
quite useful, particularly to reduce editor/admin workload.
However, although not a massive project, it would take a fair
amount of time to code. One particular difficultly would be how
to model modifying a single entry in a multiple field. I think
some of the better aspects of batch edit user interface could be
taken to help facilitate this.<br>
</p>
<p>Regards</p>
<p>David Newman<br>
</p>
<div class="moz-cite-prefix">On 17/08/2021 14:59, Martin Braendle
via Eprints-tech wrote:<br>
</div>
<blockquote type="cite" cite="mid:EMEW3|4bd62377c97c347966365b6dcb006170x7GExx14eprints-tech-bounces|ecs.soton.ac.uk|OFCB92B221.D36FDA91-ONC1258734.004C9DFF-C1258734.004CD50F@lotus.uzh.ch">
<div style="padding-bottom: 10px; padding-top: 5px;">
<div style="padding:12px; border:1px solid #8D3970;
background-color:#F7F9FA; color:#8D3970; font-size:14px;
line-height:22px; font-family: Calibri, Arial, Helvetica,
sans-serif;">
<strong>CAUTION:</strong> This e-mail originated outside the
University of Southampton.
</div>
</div>
<div>
<p><font size="2" face="sans-serif">Hi,</font><br>
<br>
<font size="2" face="sans-serif">is it possible to give a
submitter a temporary privilege to edit an item owned by
another user? Any security objections? The privilege would
be set and removed via a plugin. Or is it a silly question,
because giving a temporary privilege would already require a
admin privilege?</font><br>
<br>
<font size="2" face="sans-serif">Background: During import via
Crossref or PubMed, we check for duplicates in the archive
and issue a warning, when the item is already available.
Currently, the submitter has then the option to send a mail
to the repo editors to ask to add his institute to the
record. In order to reduce editors' workload, we would like
that that the submitter can add the his/her institute to the
item (owned by different submitter) via a button.</font><br>
<br>
<font size="2" face="sans-serif">Or should we think the other
way 'round: Assign ownership of the item temporarily to the
current submitter?</font><br>
<br>
<font size="2" face="sans-serif">Kind regards,</font><br>
<br>
<font size="2" face="sans-serif">Martin</font><br>
<br>
<br>
<font size="2" face="sans-serif">--</font><br>
<font size="2" face="sans-serif">Dr. Martin Brändle</font><br>
<font size="2" face="sans-serif">Zentrale Informatik</font><br>
<font size="2" face="sans-serif">Universität Zürich</font><br>
<font size="2" face="sans-serif">Stampfenbachstr. 73</font><br>
<font size="2" face="sans-serif">CH-8006 Zürich</font><br>
</p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">*** Options: <a class="moz-txt-link-freetext" href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a>
*** Archive: <a class="moz-txt-link-freetext" href="https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C688e3cb20f2242e932cf08d9618bb993%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637648074997178636%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=XB8emjl%2BxRhO4ZB7t0UPSY%2BS%2BloqDKpWLcymWBWsQNM%3D&reserved=0" originalSrc="http://www.eprints.org/tech.php/" shash="d87A4vNf6UKsM/CkHXkDx7KD3sW7SojlCgv82+M4QpcyYNYkC45BpL+EBrCiyIg8SzXQ1eZ+4L8fT5eb+R5wbSjYJJgNIGSBhTyN+dw2JYJTMN7A8b0qzAt5fF7SnFfaxJNY9KXNF5F0dJWTAyMhDQzDqX0eCKtq4ZXY4RC+vaU=">http://www.eprints.org/tech.php/</a>
*** EPrints community wiki: <a class="moz-txt-link-freetext" href="https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C688e3cb20f2242e932cf08d9618bb993%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637648074997178636%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Q4y2rE2KLQ6E%2B3gvn0sP9zHI4hngO%2B0PXssiezo2BAM%3D&reserved=0" originalSrc="http://wiki.eprints.org/" shash="Vqs2us/QEfA7/1Kuwdsqz2EsA0BarPA1w1bVYiqv4Xl7LV6kYuZ7qUK3YFkkAqmSAMI2x/A/sZLxr2fYjggAhMytNJr9LGwm1YcpaOeVZHZqG5pyB1A0upqj79RpHWsKBrooQS0mS9ed8InJCRBjsI45ur86GTHu717dW5axx3I=">http://wiki.eprints.org/</a></pre>
</blockquote>
<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2">
<br><br>
<hr style="border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;">
<table style="border-collapse:collapse;border:none;">
<tr>
<td style="border:none;padding:0px 15px 0px 8px">
<a href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.avg.com%2Finternet-security&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C688e3cb20f2242e932cf08d9618bb993%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637648074997188591%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3o%2FE%2F4BqWZ3o5gLVzIcI2QZGJ7EvX8fiuwKV%2BpUuj%2FE%3D&reserved=0" originalSrc="https://www.avg.com/internet-security" shash="qHZPca6tTg0wHXFzv1IhwmecV+cQZSNuvXBbUaAWQ9Zn0v4/r19yU2jNAv/47Cfjsup+czU1WhatEs3usUt8TBarbDz0auV8a1y1eabDki0+7RNi2qOTLT/qjSFBzec2NN8JdqPE68CYKcJ3WqTfMBHilA0N3NRIi9c40Xt5yEg=">
<img border="0" src="https://static.avast.com/emails/avg-mail-stamp.png" alt="AVG logo">
</a>
</td>
<td>
<p style="color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;">
This email has been checked for viruses by AVG antivirus software.
<br><a href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.avg.com%2Finternet-security&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C688e3cb20f2242e932cf08d9618bb993%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637648074997188591%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3o%2FE%2F4BqWZ3o5gLVzIcI2QZGJ7EvX8fiuwKV%2BpUuj%2FE%3D&reserved=0" originalSrc="https://www.avg.com/internet-security" shash="qHZPca6tTg0wHXFzv1IhwmecV+cQZSNuvXBbUaAWQ9Zn0v4/r19yU2jNAv/47Cfjsup+czU1WhatEs3usUt8TBarbDz0auV8a1y1eabDki0+7RNi2qOTLT/qjSFBzec2NN8JdqPE68CYKcJ3WqTfMBHilA0N3NRIi9c40Xt5yEg=">www.avg.com</a>
</p>
</td>
</tr>
</table>
<br>
<a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body>
</html>