<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<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>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi James,<br>
ExifTool is perfect for this*... if I manage to get my act together, I'll release a plugin before Easter that will do magic things. It's been waiting in the wings for far too long.
<span contenteditable="false" id="😕">😕</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Cheers,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
John</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
*once you work out that EPrints does some helpful things with files/File::Temp objects that may confuse the hell out of you</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> eprints-tech-bounces@ecs.soton.ac.uk <eprints-tech-bounces@ecs.soton.ac.uk> on behalf of James Kerwin via Eprints-tech <eprints-tech@ecs.soton.ac.uk><br>
<b>Sent:</b> 30 March 2022 16:24<br>
<b>To:</b> eprints-tech@ecs.soton.ac.uk <eprints-tech@ecs.soton.ac.uk><br>
<b>Subject:</b> [EP-tech] Plan S - exiftool - Embed license in metadata</font>
<div> </div>
</div>
<div>
<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>
<div dir="ltr">Hi All,<br>
<div><br>
</div>
<div>Please tell me if there is a more appropriate place to ask this.</div>
<div><br>
</div>
<div>I have a couple more server upgrades to do, but after that I hope to move on to the Plan S work that is outstanding. Specifically the exiftool installation and setup for the following Plan S point (<a href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.coalition-s.org%2Fplan-s-practical-advice%2F%23%3A~%3Atext%3DPlan%2520S%2520requires%2520that%2520publishers%2Cset%2520up%2520to%2520facilitate%2520this.&data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C61c76c5bee044bc94ca208da126e6feb%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637842562771857129%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=nUKWMAItxrrp3hIsQkL%2BxyOiPCdn2fXcsTlnRjU0HUw%3D&reserved=0" originalSrc="https://www.coalition-s.org/plan-s-practical-advice/#:~:text=Plan%20S%20requires%20that%20publishers,set%20up%20to%20facilitate%20this." shash="HgPE93qTjCyhcjClrNjqx6UtaZ9WgMwiQ1utS96kUSJHFgb0fBRvVN3L7davu8ejRJBnyhwz8CyHZa9G9dtM/Oob4hMEQZ+P7anHAiz6vo+Y2zN8jb/+M4R8BmbdGBbnOpYUSY7I4S/8tWscPhXo+l/f/jH395DGROO/gWIWLWM=" originalsrc="https://www.coalition-s.org/plan-s-practical-advice/#:~:text=Plan%20S%20requires%20that%20publishers,set%20up%20to%20facilitate%20this." shash="wRTpaYNFbRDvxoPdUjZywgdfwQ3g8QsnA6DSjvytZIucwIRts1gDzrXAFr/08pbGxoGmcl2SZTWmwbihYNK6V9n2funLEfUp0cB0Lc25g9NNxr1s73YCztZ8qGQH4OI08iXu/XV32eTUr5z0E9OXam+RsmtIThozB6zSvWyLBf4=" originalsrc="https://www.coalition-s.org/plan-s-practical-advice/#:~:text=Plan%20S%20requires%20that%20publishers,set%20up%20to%20facilitate%20this." shash="OiSgXsLeb4OsuWybeAyMgJhdMaMq/YjVoJqmfIF6l3ZaX71gvRXIWtSEHoUCRnEnxrZcS+5cObvQTY1/yJRj2Tj50tBBQ5VgSQ8rZcmpj0rgAvtoaChqGZTfO8t7QU0NAortMubBvPbLqD4H18Rv9OudGiL29ntUVBKMopOUdtk=">https://www.coalition-s.org/plan-s-practical-advice/#:~:text=Plan%20S%20requires%20that%20publishers,set%20up%20to%20facilitate%20this.</a>):</div>
<div><br>
</div>
<div>"Machine-readable information on the Open Access status and the license embedded in the article, in a standard non-proprietary format."</div>
<div><br>
</div>
<div>I'm not really sure how to go about this, but I think I can bumble through it.</div>
<div><br>
</div>
<div>Does anybody have any strong opinions on the suitability of exiftool? Will the exiftool perl module be sufficient for this very specific use or am I better going for the non-Perl full version?</div>
<div><br>
</div>
<div>I do also have some questions around the "machine readable" part of this point, specifically for the mitigations for organisations that can't embed metadata in the files, but maybe this isn't the place for it (if anyone would like a talk about it outside
of this list please email me!).</div>
<div><br>
</div>
<div>Thanks,</div>
<div>James</div>
</div>
</div>
</div>
</div>
</body>
</html>