<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>
<div>
<div style="direction:ltr">Hi Beth</div>
<div><br>
</div>
<div style="direction:ltr">I had a long call with Thomas Orrell about your case. I understood from that, the SI put ARKs (through EZID) on your records, assets and datasets in upstream systems which will still operate normally with an IPT (i.e. you map them
to your occurrenceID). The IPT can be configured to issue dataset level identifiers by authenticating directly with EZID. It is that integration we believe now has issue but is not being used to our knowledge. Please say if you think otherwise though.</div>
<div><br>
</div>
<div style="direction:ltr">Thanks </div>
<div style="direction:ltr">Tim</div>
</div>
<div><br>
</div>
<div class="x_ms-outlook-ios-signature">Get <a href="https://aka.ms/o0ukef">Outlook for iOS</a></div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> IPT <ipt-bounces@lists.gbif.org> on behalf of Gamble, Beth <GambleB@si.edu><br>
<b>Sent:</b> Monday, July 8, 2019 8:33:22 PM<br>
<b>To:</b> ipt@lists.gbif.org<br>
<b>Cc:</b> Orrell, Thomas; Snyder, Rebecca<br>
<b>Subject:</b> Re: [IPT] EZID, ARK and DOI</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hello Tim,<br>
<br>
The Smithsonian Institution National Museum of Natural History (NMNH) uses EZIDs as our unique identifiers. What EZID capability are you removing from IPT?
<br>
<br>
Beth :-)<br>
<br>
Beth Gamble<br>
Senior Systems Analyst<br>
IT - Informatics Office<br>
w 202.633.0851 e gambleb@si.edu<br>
<br>
SMITHSONIAN INSTITUTION<br>
NATIONAL MUSEUM OF NATURAL HISTORY<br>
Facebook | Twitter | Instagram<br>
<br>
-----Original Message-----<br>
<br>
Date: Wed, 19 Jun 2019 08:38:01 +0000<br>
From: Tim Robertson <trobertson@gbif.org><br>
To: "ipt@lists.gbif.org" <ipt@lists.gbif.org><br>
Cc: informatics <informatics@gbif.org><br>
Subject: [IPT] EZID, ARK and DOI<br>
Message-ID: <E8F22A9E-D94A-430E-AE4A-BB7138ADB521@gbif.org><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear all,<br>
<br>
This email only affects those of you using DOI or EZID directly with your IPT.<br>
<br>
The next release of the IPT will be prepared to accommodate recent changes in the DataCite API who have deprecated their public API.<br>
<br>
In addition we are aware that EZID have reduced their capabilities with respect to DOIs. We are not aware of anyone using EZID as an identity service for ARKs.<br>
We therefore propose to remove EZID capabilities from the IPT 2.4 release as we are not aware that it is in use by anyone.<br>
<br>
If you are using EZID with your IPT can you please let me know asap and elaborate on which identifier scheme you are using so we can reconsider?<br>
<br>
Many thanks,<br>
Tim<br>
<br>
_______________________________________________<br>
IPT mailing list<br>
IPT@lists.gbif.org<br>
<a href="https://lists.gbif.org/mailman/listinfo/ipt">https://lists.gbif.org/mailman/listinfo/ipt</a><br>
</div>
</span></font>
</body>
</html>