[LTER-im] Questions about deprecating the LTER Data Portal...

[Mark Servilla]

Hi Marty,

Great question! The short answer is that it will not affect the LTER
DataONE member node in any way. Both the LTER and EDI member nodes are
services dependent only on the underlying EDI/PASTA data repository and
have no functional relationship to either data portal. Thanks for asking!

Sincerely,
Mark

---
Mark Servilla
mark.servilla at gmail.com


On Tue, Mar 3, 2020 at 10:43 PM Marty Downs <downs at nceas.ucsb.edu> wrote:

> Hi Mark-
> The question came up in a meeting today of how the change may affect the
> LTER DataONE node. That's an aspect we hadn't considered in the EB
> discussion.
>
> Any thoughts?
>
> Marty
>
> Please excuse typos and brevity.
>
> Marty Downs
> Director, LTER Network Office
> National Center for Ecological Analysis and Synthesis, UC Santa Barbara
> 617-833-7930 (c)
> 805-893-7549 (o)
>
>
> On Tue, Mar 3, 2020, 8:31 PM Mark Servilla <mark.servilla at gmail.com>
> wrote:
>
>> Dear IMs,
>>
>> A few questions have been asked to me directly regarding my recent email
>> about deprecating the LTER Data Portal. Let me summarize my answers for the
>> entire IM community in case others have similar questions. Also, please
>> feel free to bring up any additional questions or concerns you may have in
>> this matter. Thank you.
>>
>> Sincerely,
>> Mark
>>
>> 1. The LTER Data Portal is very different from PASTA: the LTER Data
>> Portal operates as a web server that is completely separate (both
>> physically and functionally) from the EDI/PASTA data repository, albeit, it
>> is dependent on the PASTA API to communicate with the repository for data
>> package related services (much in the same way that the EDI Data Portal is
>> dependent on the PASTA API). As such, deprecation of the LTER Data Portal
>> will not affect PASTA, or your use of the PASTA API, in any way. Rest
>> assured that you will not have to change or modify your data package
>> publishing or catalog work-flow if you use the PASTA REST web-service API
>> directly (e.g., https://pasta.lternet.edu/package/eml/...).
>>
>> 2. If your site's Internet website or other related documentation
>> references the LTER Data Portal URL address "
>> https://portal.lternet.edu/nis", you should change the LTER Data Portal
>> URL address to reference the EDI Data Portal URL address "
>> https://portal.edirepository.org/nis" prior to the LTER Data Portal's
>> final shut-down date (late summer 2020; specific date TBD). Once shut-down,
>> attempts to reach the LTER Data Portal will result in a "Site cannot be
>> reached" error in your web browser.
>>
>> 3. Data packages that have been published and archived through the LTER
>> Data Portal are also accessible through the EDI Data Portal (and vice
>> versa). Regardless of which data portal is used to initiate the archive
>> process, all data packages are ultimately archived in the EDI/PASTA data
>> repository. As a matter of course, the features found on the EDI Data
>> Portal are both equivalent to and exceed those of the LTER Data Portal. For
>> this reason, you should not experience any functional depreciation in your
>> day-to-day repository needs when using the EDI Data Portal.
>>
>> 4. As a member of the LTER Information Manager community you should
>> continue the use of your site or personal LTER LDAP credentials when
>> authenticating (i.e., "logging on") to the EDI/PASTA data repository
>> through the EDI Data Portal. One subtle difference from the LTER Data
>> Portal, however, is that you will have to actively select the "LTER"
>> affiliation at the bottom of the login web page when authenticating through
>> the EDI Data Portal since the default affiliation is set to "EDI".
>>
>> ---
>> Mark Servilla
>> mark.servilla at gmail.com
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lternet.edu/pipermail/im/attachments/20200304/6aefdb08/attachment.html>