diff --git a/_quarto.yml b/_quarto.yml index 25c0b43..6472950 100644 --- a/_quarto.yml +++ b/_quarto.yml @@ -24,25 +24,19 @@ website: href: im/new-to-lter.qmd - text: "New to IM" href: im/new-to-im.qmd - - text: "EML" - href: im/eml.qmd - - text: "GitHub Organizations" - href: im/github-organization-recs.qmd - - text: "Site Identifier" - href: im/site-identifier.qmd - - text: "Site Personnel" + - text: "Get Help" + href: im/getting-help.qmd + - text: "Update People" href: im/site-personnel.qmd - - text: "Site Publications" + - text: "Update Pubs" href: im/site-publications.qmd - - text: "Site Websites" + - text: "Websites" href: im/site-websites.qmd - - text: "Bibtex" - href: im/bibtex.qmd - - text: "Biblio Fields" - href: im/biblio-fields.qmd - - text: "Getting Help" - href: im/getting-help.qmd - - text: "Editing IM Docs" + - text: "Write EML" + href: im/eml.qmd + - text: "Site GitHub Orgs" + href: im/github-organization-recs.qmd + - text: "Suggest Edits" href: im/edits.qmd right: - icon: github diff --git a/im/eml.qmd b/im/eml.qmd index daad333..fb7716f 100644 --- a/im/eml.qmd +++ b/im/eml.qmd @@ -1,42 +1,32 @@ --- -title: "Ecological Metadata Language (EML)" +title: "Creating EML" format: html --- -## Creating EML - -The [Ecological Metadata Language (EML)](https://eml.ecoinformatics.org/) is an XML schema for describing ecological datasets. -EDI maintains [best practices for EML](https://ediorg.github.io/data-package-best-practices/) that you should review when writing your own EML. - -There are many one-off solutions for creating EML at LTER sites. Some common ones are listed below, as well as some newer offerings from EDI. +The [Ecological Metadata Language (EML)](https://eml.ecoinformatics.org/) is an XML schema for describing ecological datasets. EDI maintains [best practices for EML](https://ediorg.github.io/data-package-best-practices/) that you should review when writing your own EML. There are many one-off solutions for creating EML at LTER sites. Some common ones are listed below, as well as some newer offerings from EDI. ## ezEML [ezEML](https://ezeml.edirepository.org) is an online form based EML editor. ezEML has developed into a very simple approach for generating metadata files at three levels: -* If you're starting from scratch or don't have much experience with metadata. -* If you need to gather metadata from a researcher or student at your site, you can let them start from a template that you have created. -* Set ezEML up for your site's metadata management: - + Import EML snippets from other files. This option lets you set up something akin to a metadata database from which to import parts needed for a new EML file. - + Import datapackages (EML and data) from the EDI repository for updates and new versions. +- If you're starting from scratch or don't have much experience with metadata. +- If you need to gather metadata from a researcher or student at your site, you can let them start from a template that you have created. +- Set ezEML up for your site's metadata management: + - Import EML snippets from other files. This option lets you set up something akin to a metadata database from which to import parts needed for a new EML file. + - Import datapackages (EML and data) from the EDI repository for updates and new versions. Extensive documentation may be found in the [user guide](https://ezeml.edirepository.org/eml/user_guide) or on [YouTube](https://www.youtube.com/playlist?list=PLi1PZkcSXdAKTtpgyHnd8GjtL6kRMMGFR). - ## LTER Core Metabase -Some LTER sites manage dataset metadata using a Postgres database schema called [Metabase](https://github.com/lter/LTER-core-metabase). -It is maintained by LTER IMs, as is the companion R code called [MetaEgress](https://github.com/BLE-LTER/MetaEgress) for generating EML from Metabase. -The original Metabase was developed at GCE, but the current version (called LTER Core Metabase) is in use at BLE and JRN. - +Some LTER sites manage dataset metadata using a Postgres database schema called [Metabase](https://github.com/lter/LTER-core-metabase). It is maintained by LTER IMs, as is the companion R code called [MetaEgress](https://github.com/BLE-LTER/MetaEgress) for generating EML from Metabase. The original Metabase was developed at GCE, but the current version (called LTER Core Metabase) is in use at BLE and JRN. ## EMLassemblyline [EMLassemblyline](https://ediorg.github.io/EMLassemblyline/) is an R package for creating EML. It is maintained by EDI and is used by several LTER sites such as HBR, JRN, NES, and NTL. - ## DEIMS DEIMS used to be a [Drupal](https://www.drupal.org/)-based solution for LTER websites. Drupal is a flexible content management system / programming environment that supports metadata based LTER websites well due to its database backend. It can also be used to generate EML. Recent efforts of upgrading from the original DEIMS to Drupal 8/9 are well documented in this [GitHub repository](https://github.com/lter/Deims7-8-Migration) and modules for extracting and ingesting metadata have been developed. diff --git a/im/getting-help.qmd b/im/getting-help.qmd index 99af1bc..57cdca5 100644 --- a/im/getting-help.qmd +++ b/im/getting-help.qmd @@ -3,14 +3,12 @@ title: "Getting IM Help" format: html --- -For general information management (IM) questions, check out the **im** channel in the [LTER Slack workspace](https://lter.slack.com/). +For general information management (IM) questions, check out the **`#im`** channel in the [LTER Slack workspace](https://lter.slack.com/). Post your question, and you'll likely get a response from other IMs active that day. -For general LTER questions, again try [Slack](https://lter.slack.com/), or just [email Marty Downs](mailto:downs@nceas.ucsb.edu), director of the LTER Network Office (LNO). -If Marty gets tired of the spam, be sure to point her to this page so she can edit it and scold Tim for posting her address. +For general LTER questions, again try [Slack](https://lter.slack.com/), or email director of the LTER Network Office (LNO) Marty Downs. For help with archiving data at the Environmental Data Initiative, [email EDI](mailto:info@edirepository.org). Or join [EDI's Slack](https://edi-got-data.slack.com). They are generally very responsive and helpful. -If you see something at an LTER site and you want to know how they did that, reach out to the IM. We're a friendly community. -Some are even eager to share because shared solutions can be more sustainable and it makes the site look good when reviews and renewals come up! +If you see something at an LTER site and you want to know how they did that, reach out to the IM. We're a friendly community. Some are even eager to share because shared solutions can be more sustainable and it makes the site look good when reviews and renewals come up! diff --git a/im/github-organization-recs.qmd b/im/github-organization-recs.qmd index ed7363d..663d436 100644 --- a/im/github-organization-recs.qmd +++ b/im/github-organization-recs.qmd @@ -13,7 +13,7 @@ The LTER Network has followed our own advice and has a GitHub Organization which ## Naming Convention -We recommend adopting a common organization naming convention so that visitors to one organization can easily find the organization of another LTER site. Six sites currently have organizations and the general naming convention is to use the three letter site abbreviation in all caps followed by a hyphen and "LTER" (e.g., "JRN-LTER"). +We recommend adopting a common organization naming convention so that visitors to one organization can easily find the organization of another LTER site. Six sites currently have organizations and the general naming convention is to use the three letter site abbreviation in all caps followed by a hyphen and "LTER" (e.g., "MSP-LTER"). Note that organization names can be changed as needed without breaking an individual user's code but the link to GitHub-hosted websites/etc. will be changed if the organization name changes. @@ -56,4 +56,3 @@ The [Beaufort Lagoon Ecosystem GitHub Organization](https://github.com/BLE-LTER) ## GitHub Organization vs. Other Platforms If you are already using a comparable non-GitHub platform (e.g., [BitBucket](https://bitbucket.org/product), [GitLab](https://about.gitlab.com/), etc.) we still recommend creating a GitHub Organization! At the very least, an organization for your site will give site researchers who do use GitHub a place to store their code and interact with peers who also use GitHub–both at and outside of your site. You can also use the description field of your organization to direct visitors to the link of whichever alternate platform your site decides best fits your needs. Finally, if a majority of sites do create their own organizations, external users will be able to use the standard naming convention to navigate among sites even in cases where each site utilizes the organization at different levels of intensity. - diff --git a/im/home.qmd b/im/home.qmd index f8a8a7a..2054965 100644 --- a/im/home.qmd +++ b/im/home.qmd @@ -7,17 +7,17 @@ This part of the website is a place for new and experienced LTER information man This facet of the website gathers the current practices and procedures that apply to information management **within the LTER Network** in one place. It does not aspire to be a single source of information and resources for information management more generally--nor even for the myriad best practices that have been established through IM collaboration in the LTER Network. -Any LTER information manager may make edits to these pages, but it is likely to be most actively updated by the LTER Network Office and the LTER IM Executive Team. All LTER Information Managers will want to "watch" the repo for updates or check back regularly. To view the source code for any of these pages, see [here](https://github.com/lter/docs-network/tree/main/im). For specific procedures on making edits to the manual, please see [CONTRIBUTING.md](https://github.com/lter/docs-network/blob/main/CONTRIBUTING.md). +Any LTER information manager may make edits to these pages, but it is likely to be most actively updated by the LTER Network Office and the LTER IM Executive Team. All LTER Information Managers will want to "watch" the repo for updates or check back regularly. To view the source code for any of these pages, see [here](https://github.com/lter/docs-network/tree/main/im). ### What Do You Need to Do? -- [I'm brand new to LTER](http://lter.github.io/im-manual/new-to-lter) -- [I'm familiar with LTER, but a new Information Manager](http://lter.github.io/im-manual/new-to-im) -- [Ask for help with something](http://lter.github.io/im-manual/getting-help) -- [Update my site's personnel](http://lter.github.io/im-manual/site-personnel) -- [Update my site's publications](https://lter.github.io/im-manual/site-publications) -- [Obtain a unique site identifier](https://lter.github.io/im-manual/site-identifier) -- [Create (or edit) a site website](https://lter.github.io/im-manual/site-websites) -- [Write Ecological Markup Language (EML)](https://lter.github.io/im-manual/eml) -- [Establish a site GitHub Repository](github-organization-recs.md) -- [Suggest edits to the IM Manual](https://lter.github.io/im-manual/edits) +- [I'm brand new to LTER](https://lter.github.io/docs-network/im/new-to-lter.html) +- [I'm familiar with LTER, but a new Information Manager](http://lter.github.io/docs-network/im/new-to-im.html) +- [Ask for help with something](http://lter.github.io/docs-network/im/getting-help.html) +- [Update my site's personnel](http://lter.github.io/docs-network/im/site-personnel.html) +- [Update my site's publications](https://lter.github.io/docs-network/im/site-publications.html) +- [Obtain a unique site identifier](https://lter.github.io/docs-network/im/site-identifier.html) +- [Create (or edit) a site website](https://lter.github.io/docs-network/im/site-websites.html) +- [Write Ecological Markup Language (EML)](https://lter.github.io/docs-network/im/eml.html) +- [Establish a site GitHub Organization](https://lter.github.io/docs-network/im/github-organization-recs.html) +- [Suggest edits to the IM Manual](https://lter.github.io/docs-network/im/edits.html) diff --git a/im/new-to-im.qmd b/im/new-to-im.qmd index fa71c4d..ef487a6 100644 --- a/im/new-to-im.qmd +++ b/im/new-to-im.qmd @@ -7,18 +7,18 @@ You're familiar with the LTER Network, but haven't worked as an information mana ## Key Resources -* [**LTER Information Management System Guidelines**](https://lternet.edu/wp-content/uploads/2018/01/LTER_IMS_Guidelines_V2_1_20180103.pdf) lays out the basic tasks and responsibilities of all LTER Information Managers. -* [**Data Package Best Practices**](https://ediorg.github.io/data-package-best-practices/) has recommendations for formatting data packages of various types including non-tabular data, and for using the Ecological Metadata Language (EML) to describe those data packages. -* [**IM Bylaws**](https://lternet.edu/wp-content/uploads/2021/07/2021-06-11-LTER_IMC_Bylaws_v4_final.pdf): The LTER Network is a highly distributed organization, but the Network also depends on information managers working together across sites as a team. The IM Committee bylaws describe how the committee runs, how its leadership (IMExec) is chosen, and what the expectations are of its member IMs. -* [**Website Design and Content Guidelines**](https://lternet.edu/wp-content/uploads/2018/05/Guidelines-for-LTER-Web-Site-Design-and-Content-revised-2018-05-17.pdf) lays out general guidelines for designing site websites. While each individual LTER site needs to fit into the structure of its parent organization(s) and uses different backend technology, all sites should maintain some common types of information. -* [**IM document archive**](https://lternet.edu/lter-document-archive/?wpv-document-types%5B%5D=information-management&wpv_aux_current_post_id=87668&wpv_aux_parent_post_id=87668&wpv_sort_orderby=post_date&wpv_sort_order=desc&wpv_view_count=87950): Based within the larger LTER document archive, the IM document repository holds current and historical versions of bylaws, annual meeting reports, working group reports and other information, which can be remarkably useful in understanding the context of the Network. -* [**Environmental Data Initiative**](https://edirepository.org/): Once the data arm of the LTER Network Office, the Environmental Data Initiative is now LTER's primary data partner and also serves a myriad of other NSF programs in Environmental Biology. In addition to data curation and infrastructure, EDI provides information management training, resources, and leadership in data harmonization for synthesis. -* [**Retired IM website**](https://spinks.kbs.msu.edu/) (login: im / pw: lter): For several years, the LTER information management community maintained a website separate from the main lternet.edu website. With the advent of EDI and its broader community resources, much of the material maintained on the old im.lternet.edu website was moved to [Environmental Data Initiative](https://environmentaldatainitiative.org/), while the LTER GitHub and Google drive supplanted the LTER-specific materials. A static copy of the old *IM* site is maintained at https://spinks.kbs.msu.edu/ (use login im and password lter) for reference, thanks to Sven Bohm. +- [**LTER Information Management System Guidelines**](https://lternet.edu/wp-content/uploads/2018/01/LTER_IMS_Guidelines_V2_1_20180103.pdf) lays out the basic tasks and responsibilities of all LTER Information Managers. +- [**Data Package Best Practices**](https://ediorg.github.io/data-package-best-practices/) has recommendations for formatting data packages of various types including non-tabular data, and for using the Ecological Metadata Language (EML) to describe those data packages. +- [**IM Bylaws**](https://lternet.edu/wp-content/uploads/2021/07/2021-06-11-LTER_IMC_Bylaws_v4_final.pdf): The LTER Network is a highly distributed organization, but the Network also depends on information managers working together across sites as a team. The IM Committee bylaws describe how the committee runs, how its leadership (IMExec) is chosen, and what the expectations are of its member IMs. +- [**Website Design and Content Guidelines**](https://lternet.edu/wp-content/uploads/2018/05/Guidelines-for-LTER-Web-Site-Design-and-Content-revised-2018-05-17.pdf) lays out general guidelines for designing site websites. While each individual LTER site needs to fit into the structure of its parent organization(s) and uses different backend technology, all sites should maintain some common types of information. +- [**IM document archive**](https://lternet.edu/lter-document-archive/?wpv-document-types%5B%5D=information-management&wpv_aux_current_post_id=87668&wpv_aux_parent_post_id=87668&wpv_sort_orderby=post_date&wpv_sort_order=desc&wpv_view_count=87950): Based within the larger LTER document archive, the IM document repository holds current and historical versions of bylaws, annual meeting reports, working group reports and other information, which can be remarkably useful in understanding the context of the Network. +- [**Environmental Data Initiative**](https://edirepository.org/): Once the data arm of the LTER Network Office, the Environmental Data Initiative is now LTER's primary data partner and also serves a myriad of other NSF programs in Environmental Biology. In addition to data curation and infrastructure, EDI provides information management training, resources, and leadership in data harmonization for synthesis. +- [**Retired IM website**](https://spinks.kbs.msu.edu/) (login: im / pw: lter): For several years, the LTER information management community maintained a website separate from the main lternet.edu website. With the advent of EDI and its broader community resources, much of the material maintained on the old im.lternet.edu website was moved to [Environmental Data Initiative](https://environmentaldatainitiative.org/), while the LTER GitHub and Google drive supplanted the LTER-specific materials. A static copy of the old IM site is maintained [here](https://spinks.kbs.msu.edu/) for reference, thanks to Sven Bohm. ## Working in a Connected Community -* **Virtual Water Coolers**: The Information Management Committee meets monthly on the second Monday of each month at noon, Pacific time. The zoom link (always the same) will be emailed to everyone on the IM email list a day or two before the meeting. Regular attendance at these "Virtual Watercoolers" is expected of all LTER information managers. Plus, it will really help you learn your way around the network, connect to colleagues, and stay painlessly up-to-date. -* **IM Annual Meeting**: Once a year, in summer or early fall, the entire group of information managers meets either in person or online to reconnect, move projects forward, and discuss new directions. These meetings usually take place in association with the LTER All Scientists Meeting or the meeting of a related society such as the Earth Science Information Partners or the Ecological Society of America. Reports from past annual meetings are found in the [document archive](https://lternet.edu/?taxonomy=document-types&term=information-management). -* [**IM Committee on LTER Community Forum**](https://lternet.discourse.group/g/information-mgrs?asc=true): Please join the LTER Community Forum and request to join the Information Managers Group and watch the Information Management category to take part in IM discussions and connect with colleagues. -* [**Shared Google Drive**](https://drive.google.com/drive/u/0/folders/0AABt1FqIzosUUk9PVA): The LTER-committee-information-management google drive contains active working documents related to IM working groups, IM Exec, Committee Meetings, recordings of recent Virtual Water Coolers and other active resources. Once documents are finalized or working groups complete their activities, long term records move to the document archive. LTER Network Office Staff or current IM Exec members can add new LTER Information Managers to the shared google drive. -* [**LTER GitHub**](https://github.com/lter): Many repositories house current and past programming projects of the LTER Network and its data partner, the Environmental Data Initiative. (Do start with the index, as there are a wide variety of projects in various stages of maintenance.) This manual is also maintained in a GitHub repo, where all LTER information managers can [make suggestions](https://lter.github.io/im-manual/edits) for additions or updates. +- **Virtual Water Coolers**: The Information Management Committee meets monthly on the second Monday of each month at noon, Pacific time. The zoom link (always the same) will be emailed to everyone on the IM email list a day or two before the meeting. Regular attendance at these "Virtual Watercoolers" is expected of all LTER information managers. Plus, it will really help you learn your way around the network, connect to colleagues, and stay painlessly up-to-date. +- **IM Annual Meeting**: Once a year, in summer or early fall, the entire group of information managers meets either in person or online to reconnect, move projects forward, and discuss new directions. These meetings usually take place in association with the LTER All Scientists Meeting or the meeting of a related society such as the Earth Science Information Partners or the Ecological Society of America. Reports from past annual meetings are found in the [document archive](https://lternet.edu/?taxonomy=document-types&term=information-management). +- [**IM Committee on LTER Community Forum**](https://lternet.discourse.group/g/information-mgrs?asc=true): Please join the LTER Community Forum and request to join the Information Managers Group and watch the Information Management category to take part in IM discussions and connect with colleagues. +- [**Shared Google Drive**](https://drive.google.com/drive/u/0/folders/0AABt1FqIzosUUk9PVA): The LTER-committee-information-management google drive contains active working documents related to IM working groups, IM Exec, Committee Meetings, recordings of recent Virtual Water Coolers and other active resources. Once documents are finalized or working groups complete their activities, long term records move to the document archive. LTER Network Office Staff or current IM Exec members can add new LTER Information Managers to the shared google drive. +- [**LTER GitHub Organization**](https://github.com/lter): Many repositories house current and past programming projects of the LTER Network and its data partner, the Environmental Data Initiative. (Do start with the index, as there are a wide variety of projects in various stages of maintenance.) This manual is also maintained in a GitHub repo, where all LTER information managers can [make suggestions](https://lter.github.io/docs-network/im/edits.html) for additions or updates. diff --git a/im/new-to-lter.qmd b/im/new-to-lter.qmd index 6b74371..400aa56 100644 --- a/im/new-to-lter.qmd +++ b/im/new-to-lter.qmd @@ -5,7 +5,7 @@ format: html Although each of the sites and roles are a bit different, overall, the LTER Network is a truly congenial, helpful, and welcoming community. These pages are intended to help you find your way around our various communication channels in your first weeks and months. -For resources specific to information management (IM), please see the **[new to LTER information management](new-to-im.md)** page. +For resources specific to information management (IM), please see the **[new to LTER information management](http://lter.github.io/docs-network/im/new-to-im.html)** page. ## Get Connected: diff --git a/im/site-personnel.qmd b/im/site-personnel.qmd index f9088eb..2d9e052 100644 --- a/im/site-personnel.qmd +++ b/im/site-personnel.qmd @@ -3,124 +3,122 @@ title: "Site Personnel Lists" format: html --- -> [!NOTE] -> -> SalesForce database has been deprecated. Personnel reporting continues in Google sheets for now, but is moving to the lternet website. Email Marty for permission to edit google sheets if you don't have it. +:::{.callout-note} +SalesForce database has been deprecated. Personnel reporting continues in Google sheets for now, but is moving to the lternet website. Email Marty for permission to edit google sheets if you don't have it. +::: + ## Overview Rather than having an individual simply associated with a site or not, we strive to maintain a record of prior associations and allow multiple simultaneous associations (with different sites, in different roles, and with different institutions) for individuals. This is valuable for understanding how individuals interact with the Network across their careers. To accomplish it, however, we need to update **affiliations**, (a record of person-site-role-time period) rather than just people's current affiliation with a site. -## Making bulk updates **(new July 27, 2024)** +## Making Bulk Updates Usually, there are a few times a year when many people need to be added at once. Edits to LTER site personnel can be made directly in [the LTERHub-ex-im google sheets document](https://docs.google.com/spreadsheets/d/1TSmzt-Cg2xIKlJ3uin8EoMclACThkPiWqwroG3JoPdQ/edit#gid=293749749). Lead site information managers and designated updaters for each site have read access to the file. Edit permissions will be granted on a sheet-by-sheet basis to one designated updater per site. - -> [!NOTE] -> Note that Google sheets, unlike Excel sheets or csv files, save data continuously as they are entered.* - -### Overall workflow ### -- Each site has its own tab in the spreadsheet. Before you plan to make edits, please identify one editor per site and request file edit access for them by emailing Marty. -- Using the instructions below, make edits to your site's personnel list. Where you do not have changes to make, simply leave the the existing information. -- Add new individuals and new affiliations to the bottom of the list, leaving the SalesForce ID columns blank -- **IMPORTANT: Notify Marty when you have made a batch of updates** - -### Individual Updates ### -For the moment, we are focused on bulk updates. The LNO will announce a new process (and training) for individual updates in the near future. - -> [!NOTE] -> The API function was part of SalesForce and was rarely used. It has been deprecated temporarily. Once the transition to website updating is complete, we can re-establish it. + +:::{.callout-note} +Note that Google sheets, unlike Excel sheets or csv files, save data continuously as they are entered. +::: -## Row and Column Descriptions ## +## Overall Workflow -#### Rows #### +- Each site has its own tab in the spreadsheet. Before you plan to make edits, please identify one editor per site and request file edit access for them by emailing Marty. +- Using the instructions below, make edits to your site's personnel list. Where you do not have changes to make, simply leave the the existing information. +- Add new individuals and new affiliations to the bottom of the list, leaving the SalesForce ID columns blank +- **IMPORTANT: Notify Marty when you have made a batch of updates** -- **Row 1** is blank -- **Row 2** lists the common-language descriptions of each field. -- **Row 3** lists the SalesForce names for each field. This assists in upload and should not be edited. -- **Data rows:** Each data row represents an **affiliation** between an individual and a site in a particular role, for a specific period of time. Thus, an individual may appear in multiple rows with different roles. Within each sheet, records are sorted first by "Current" or "Former" status and then alphabetically by last name. Be aware that the same individual may have both current and former affiliations, or may have multiple current affiliations. +## Individual Updates -#### Columns #### +For the moment, we are focused on bulk updates. The LNO will announce a new process (and training) for individual updates in the near future. -- **Database Keys:** - - A. **Affiliation ID** *(protected)*: The unique key for the specific affiliation (role-site/institution-individual combination) - - B. **Contact ID** *(protected)*: The unique key for the individual contact associated with that affiliation - - C. **Account ID** *(protected)*: The unique key for the account (site or institution) associated with that affiliation - - D. **Profile ID** *(protected)*: The unique key for the user associated with that affiliation - -- **Site Information:** - - E. **Acronym**: The 3-letter site acronym. This should **always** match the spreadsheet tab in which you are editing. If an affiliation with a different site needs to be created or edited, that should be done by the individual or by the designated editor for that site. - -- **Contact-related information:** - - F. **Last Name**: Last name of the individual contact. Text fields can accept both hyphenated and un-hyphenated names. Special characters may be used with caution, but HTML formatting is not permitted. - - G. **First Name**: First name of the individual contact - - H. **Middle Name**: Middle name or initial of the individual contact (if known). If initials are used, please include a period. - - I. **Email**: Active email address of the individual contact. Be cautious in changing this. It also serves as the user's login and (especially for former site participants) you may not have the most current information. - - J. **ORCID**: Once entered, this is unlikely to change. Users will be prompted to update ORCIDs on site registration. - - P. **Contact-Site ID**: If your site uses a unique identifier for individuals that could aid in matching site and network-level information, this is the place to enter it. If you do not use such a system, please leave this field blank. *(Located at the end as only a few sites use this field.)* - -- **Affiliation-related information:** - - K. **Role (Affiliation)**: Recall that participants may have multiple simultaneous affiliations. This field holds the role for one affiliation with a particular site. The (limited) choices for this field are available in the drop down. Please DO NOT add choices that do not appear in the drop down selector. [Options for "Role"](#Detailed-Field-descriptions-and-options) are detailed later on this page. - - L. **Start Year (Affiliation)**: The year that this affiliation started - to the best of your knowledge. This information is not strictly required and participants can update this information directly when they register on the site. - - M. **End Year (Affiliation)**: The year that this affiliation ended - to the best of your knowledge. This information is not strictly required and participants can update this information directly when they register on the site. When an entered end year is less than the current year, the affiliation status will be automatically converted to "Former" at the time data is uploaded. - - N. **Status (Affiliation)**: Status" has 2 options: "Current" or "Former." This reflects an individual's affiliation *with the site*. All newly affiliated individuals should be listed as "Current." When an individual leaves your site, they should be identified as "Former" for your site and an end date entered for their role. When their status changes to "Former" at all sites with which they had an affiliation, their LTER status will automatically change to "Inactive". As long as they maintain an active affiliation with any LTER site, their LTER status will be "Active." This field controls whether individuals appear in the site directory for the affiliated site. - - O. **Primary (Affiliation)**: This Boolean field identifies *this* affiliation as the primary one (across all LTER associations) for the associated individual. In general, it should be set by the individual during the registration process. Among several possible affiliations, it will usually be the most active or the most recent. - -- **User-related information:** - - Q. **Active User?**: This field contains a Boolean (true/false) value indicting whether a user has been activated for this contact. - -- **Upload/Update results columns**: Columns S and beyond are used to store the result of the most recent uploads to SalesForce. Failures may indicate duplicate names or other conditions that require investigation. They should not be edited except by the LNO. - -### Specific Use Cases ### - -* **New participants:** Add new site participants at the bottom of your site's sheet, below the existing entries. Often, individuals who are new to your site actually have a prior LTER identity. When they are using the same email address, these duplicates will be caught on creation. If they are using a new email address, the LNO will eventually find and resolve them. For new participants with more than one role, include only the primary role at this stage. Follow the instructions below for "adding roles" to add additional affiliations. Fill in: - * Last Name - * First Name - * Middle Name (if known) - * Email - * ORCID (if known): Use the full http format, e.g https://orcid.org/0000-0003-2833-956X - * Role (with respect to your site): If the individual will hold multiple roles, add them each on a new line. - * Start Year (Affiliation): For new individuals, this will typically be the current year. - * End Year (Affiliation): For new individuals, leave this blank. - * Status (Affiliation): Choose "Current" - * Primary (Affiliation): If you are quite confident that this affiliation is the primary LTER affiliation for this individual, enter TRUE or conversely, FALSE. Otherwise, leave this field blank. - * Contact-Site ID: If your site uses this field, enter the site-id for the individual. Enter the same site-id for all affiliations that individual may have with your site. If your site doesn't use this field (most sites) leave it blank. - * Active User?: **Leave this field blank** - -* **Adding roles:** Add new roles at the bottom of your site's sheet, below the existing entries and the new participants. Separate new roles from new participants with a blank line. Copy contact-related information (Last Name, First Name, Middle Name, Email, and ORCID) from an existing affiliation for that individual and update the affiliation-related information as needed. - -* **Ending roles:** To end a role for an individual, simply enter the year that they stopped serving in that role into the "End Year (Affiliation)" field. If they never served that role, please contact Marty Downs (downs@nceas.ucsb.edu) for troubleshooting assistance. - -* **Former participants:** -> [!WARNING] -> We are currently resolving an issue with the display of former participants on the [LTER directory](https://lternet.edu/directory/). For the moment, please ensure that the affiliation status in the LTER-ex-im Google sheet is correct and we will resolve the directory display as soon as possible. +:::{.callout-note} +The API function was part of SalesForce and was rarely used. It has been deprecated temporarily. Once the transition to website updating is complete, we can re-establish it. +::: + +## Row and Column Descriptions + +### Rows + +- **Row 1** is blank +- **Row 2** lists the common-language descriptions of each field. +- **Row 3** lists the SalesForce names for each field. This assists in upload and should not be edited. +- **Data rows:** Each data row represents an **affiliation** between an individual and a site in a particular role, for a specific period of time. Thus, an individual may appear in multiple rows with different roles. Within each sheet, records are sorted first by "Current" or "Former" status and then alphabetically by last name. Be aware that the same individual may have both current and former affiliations, or may have multiple current affiliations. + +### Columns + +- **Database Keys:** + - A. **Affiliation ID** *(protected)*: The unique key for the specific affiliation (role-site/institution-individual combination) + - B. **Contact ID** *(protected)*: The unique key for the individual contact associated with that affiliation + - C. **Account ID** *(protected)*: The unique key for the account (site or institution) associated with that affiliation + - D. **Profile ID** *(protected)*: The unique key for the user associated with that affiliation +- **Site Information:** + - E. **Acronym**: The 3-letter site acronym. This should **always** match the spreadsheet tab in which you are editing. If an affiliation with a different site needs to be created or edited, that should be done by the individual or by the designated editor for that site. +- **Contact-related information:** + - F. **Last Name**: Last name of the individual contact. Text fields can accept both hyphenated and un-hyphenated names. Special characters may be used with caution, but HTML formatting is not permitted. + - G. **First Name**: First name of the individual contact + - H. **Middle Name**: Middle name or initial of the individual contact (if known). If initials are used, please include a period. + - I. **Email**: Active email address of the individual contact. Be cautious in changing this. It also serves as the user's login and (especially for former site participants) you may not have the most current information. + - J. **ORCID**: Once entered, this is unlikely to change. Users will be prompted to update ORCIDs on site registration. + - P. **Contact-Site ID**: If your site uses a unique identifier for individuals that could aid in matching site and network-level information, this is the place to enter it. If you do not use such a system, please leave this field blank. _Located at the end as only a few sites use this field._ +- **Affiliation-related information:** + - K. **Role (Affiliation)**: Recall that participants may have multiple simultaneous affiliations. This field holds the role for one affiliation with a particular site. The (limited) choices for this field are available in the drop down. Please DO NOT add choices that do not appear in the drop down selector. [Options for "Role"](#Detailed-Field-descriptions-and-options) are detailed later on this page. + - L. **Start Year (Affiliation)**: The year that this affiliation started - to the best of your knowledge. This information is not strictly required and participants can update this information directly when they register on the site. + - M. **End Year (Affiliation)**: The year that this affiliation ended - to the best of your knowledge. This information is not strictly required and participants can update this information directly when they register on the site. When an entered end year is less than the current year, the affiliation status will be automatically converted to "Former" at the time data is uploaded. + - N. **Status (Affiliation)**: Status" has 2 options: "Current" or "Former." This reflects an individual's affiliation _with the site_. All newly affiliated individuals should be listed as "Current." When an individual leaves your site, they should be identified as "Former" for your site and an end date entered for their role. When their status changes to "Former" at all sites with which they had an affiliation, their LTER status will automatically change to "Inactive". As long as they maintain an active affiliation with any LTER site, their LTER status will be "Active." This field controls whether individuals appear in the site directory for the affiliated site. + - O. **Primary (Affiliation)**: This Boolean field identifies _this_ affiliation as the primary one (across all LTER associations) for the associated individual. In general, it should be set by the individual during the registration process. Among several possible affiliations, it will usually be the most active or the most recent. +- **User-related information:** + - Q. **Active User?**: This field contains a Boolean (true/false) value indicting whether a user has been activated for this contact. +- **Upload/Update results columns**: Columns S and beyond are used to store the result of the most recent uploads to SalesForce. Failures may indicate duplicate names or other conditions that require investigation. They should not be edited except by the LNO. + +## Specific Use Cases + +- **New participants:** Add new site participants at the bottom of your site's sheet, below the existing entries. Often, individuals who are new to your site actually have a prior LTER identity. When they are using the same email address, these duplicates will be caught on creation. If they are using a new email address, the LNO will eventually find and resolve them. For new participants with more than one role, include only the primary role at this stage. Follow the instructions below for "adding roles" to add additional affiliations. Fill in: + - Last Name + - First Name + - Middle Name (if known) + - Email + - ORCID (if known): Use the _full http format_, e.g., https://orcid.org/0000-0003-2833-956X rather than just the numbers + - Role (with respect to your site): If the individual will hold multiple roles, add them each on a new line. + - Start Year (Affiliation): For new individuals, this will typically be the current year. + - End Year (Affiliation): For new individuals, leave this blank. + - Status (Affiliation): Choose "Current" + - Primary (Affiliation): If you are quite confident that this affiliation is the primary LTER affiliation for this individual, enter TRUE or conversely, FALSE. Otherwise, leave this field blank. + - Contact-Site ID: If your site uses this field, enter the site-id for the individual. Enter the same site-id for all affiliations that individual may have with your site. If your site doesn't use this field (most sites) leave it blank. + - Active User?: **_Leave this field blank_** +- **Adding roles:** Add new roles at the bottom of your site's sheet, below the existing entries and the new participants. Separate new roles from new participants with a blank line. Copy contact-related information (Last Name, First Name, Middle Name, Email, and ORCID) from an existing affiliation for that individual and update the affiliation-related information as needed. +- **Ending roles:** To end a role for an individual, simply enter the year that they stopped serving in that role into the "End Year (Affiliation)" field. If they never served that role, please contact Marty Downs (downs@nceas.ucsb.edu) for troubleshooting assistance. +- **Former participants:** + +:::{.callout-warning} +We are currently resolving an issue with the display of former participants on the [LTER directory](https://lternet.edu/directory/). For the moment, please ensure that the affiliation status in the LTER-ex-im Google sheet is correct and we will resolve the directory display as soon as possible. +::: Once an individual has left the site, please change their "Status (Affiliation)" field to "Former". If you can make a fair guess at an end year, include that information under "End Year". If you can't guess within a year or two, leave it blank. -## Detailed Field descriptions and options +## Detailed Field Descriptions A few fields use limited options and will not accept any text other than the below. -* Site options: AND, ARC, BES, BLE, BNZ, CAP, CCE, CDR, CWT, FCE, GCE, HBR, HFR, JRN, KBS, KNZ, LUQ, MCM, MCR, MSP, NES, NGA, NTL, NWT, PAL, PIE, SBC, SEV, SGS, VCR - * Special Options: EDI, LNO, INT, NWK are for personnel associated with the Environmental Data Initiative (EDI), LTER Network Office (LNO), International LTER (INT), and the Network as a whole (NWK)--for example, staff of related organizations and networks. -* Site Role: - * **Lead Principal Investigator:** The primary individual who is responsible for the scientific or technical direction of the project. - * **Co-Principal Investigator:** The individuals who are formally responsible for the scientific or technical direction of the project. (Cover page investigators.) - * **Investigator:** An individual with substantial scientific involvement in the LTER, but who is not a Co-Principal Investigator(s). LTER Investigators need not be funded by the project. - * **Postdoctoral Associate:** An individual with a doctoral-level degree who does research at the site, but does not hold a permanent position. Generally Postdocs are less than 5 years post-degree. - * **Graduate Student:** A part-time or full-time student working on the project in a research capacity who holds at least a bachelor's degree and is enrolled in a degree program leading to an advanced degree. - * **Postbac Associate:** A recent graduate in a short-term training position. (i.e. Postbac, as distinguished from an ongoing technical or research position.) - * **Undergraduate Student:** A student working on the project in a research capacity who is enrolled in a degree program (part-time or full-time) leading to a bachelor's or associate's degree. - * **Information Manager:** A person at an LTER site that spends some or all of their time in the process of data and information management. This person may or may not be the site representative to the information management committee. - * **Education Manager:** A person at an LTER site that spends some or all of their time in the process of education/outreach. This person may or may not be the site representative to the education/outreach committee. - * **Other Professional:** A person who may or may not hold a doctoral degree or its equivalent, who is considered a professional and is not reported as a Principal Investigator, Co-principal Investigator, Investigator, Postdoctoral Associate or Student. Examples include research associates, physicians, veterinarians, system experts, computer programmers and design engineers. - * **Technical/Research Staff:** Technicians and field research personnel. - * **Education/Communications Staff:** Educators or science-focused communicators. - * **Administrative Staff:** Persons working on the project in a non-research capacity in an administrative role. - * **Other Staff:** Persons working on the project in a non-research capacity, such as draftsmen, animal caretakers, electricians and custodial personnel. - * **Interested Party:** A person who is associated with an LTER site or the Network through interest, educational programs, public outreach etc., may include educational or community partners, neighbors, board members, etc. - * **Retired:** _Emeritus_ Investigators who maintain an active interest in the site and the Network. Not necessarily the same as past network members (who are designated as "Former"). - -* Less-frequently used Site Role options, for individuals that you want to associate with your site in specific roles: - * K-12 Teacher - * Volunteer - * Media +- Site options: AND, ARC, BES, BLE, BNZ, CAP, CCE, CDR, CWT, FCE, GCE, HBR, HFR, JRN, KBS, KNZ, LUQ, MCM, MCR, MSP, NES, NGA, NTL, NWT, PAL, PIE, SBC, SEV, SGS, VCR + - Special Options: EDI, LNO, INT, NWK are for personnel associated with the Environmental Data Initiative (EDI), LTER Network Office (LNO), International LTER (INT), and the Network as a whole (NWK)--for example, staff of related organizations and networks. +- Site Role: + - **Lead Principal Investigator:** The primary individual who is responsible for the scientific or technical direction of the project. + - **Co-Principal Investigator:** The individuals who are formally responsible for the scientific or technical direction of the project. (Cover page investigators.) + - **Investigator:** An individual with substantial scientific involvement in the LTER, but who is not a Co-Principal Investigator(s). LTER Investigators need not be funded by the project. + - **Postdoctoral Associate:** An individual with a doctoral-level degree who does research at the site, but does not hold a permanent position. Generally Postdocs are less than 5 years post-degree. + - **Graduate Student:** A part-time or full-time student working on the project in a research capacity who holds at least a bachelor's degree and is enrolled in a degree program leading to an advanced degree. + - **Postbac Associate:** A recent graduate in a short-term training position. (i.e. Postbac, as distinguished from an ongoing technical or research position.) + - **Undergraduate Student:** A student working on the project in a research capacity who is enrolled in a degree program (part-time or full-time) leading to a bachelor's or associate's degree. + - **Information Manager:** A person at an LTER site that spends some or all of their time in the process of data and information management. This person may or may not be the site representative to the information management committee. + - **Education Manager:** A person at an LTER site that spends some or all of their time in the process of education/outreach. This person may or may not be the site representative to the education/outreach committee. + - **Other Professional:** A person who may or may not hold a doctoral degree or its equivalent, who is considered a professional and is not reported as a Principal Investigator, Co-principal Investigator, Investigator, Postdoctoral Associate or Student. Examples include research associates, physicians, veterinarians, system experts, computer programmers and design engineers. + - **Technical/Research Staff:** Technicians and field research personnel. + - **Education/Communications Staff:** Educators or science-focused communicators. + - **Administrative Staff:** Persons working on the project in a non-research capacity in an administrative role. + - **Other Staff:** Persons working on the project in a non-research capacity, such as draftsmen, animal caretakers, electricians and custodial personnel. + - **Interested Party:** A person who is associated with an LTER site or the Network through interest, educational programs, public outreach etc., may include educational or community partners, neighbors, board members, etc. + - **Retired:** _Emeritus_ investigators who maintain an active interest in the site and the Network. Not necessarily the same as past network members (who are designated as "Former"). +- Less-frequently used Site Role options, for individuals that you want to associate with your site in specific roles: + - K-12 Teacher + - Volunteer + - Media diff --git a/im/site-publications.qmd b/im/site-publications.qmd index fe72bc9..e2b8238 100644 --- a/im/site-publications.qmd +++ b/im/site-publications.qmd @@ -1,28 +1,32 @@ --- -title: "Site Publications" +title: "LTER Publications" format: html --- -## Tracking and Sharing LTER Publications # +## Tracking and Sharing The LTER Network maintains a [Zotero group library](https://www.zotero.org/groups/2055673/lter_network/library) where we track publications (journal articles, reports, and theses) that have been made possible through LTER funding, collaborations, and activities. It does not include publications that preceded LTER funding at sites that now house LTER programs. The [publications web page](https://lternet.edu/bibliography/) on the LTER Network website draws its data from the Zotero library. The LTER Network Office searches Web of Science monthly for all LTER grant numbers in the ackowledgements field and adds found publications to the library. We strongly encourage sites to update their publication lists at least annually (generally around the time of their annual report to NSF) beacuse our search strategy does not catch theses or publications where authors have not acknowledged your site by grant number. -**Please include** +:::{.panel-tabset} +### Please include -Journal articles, books, book chapters, maps, software, peer-reviewed conference papers (not posters or presentations), published reports, patents, Master’s and PhD theses. +Journal articles, books, book chapters, maps, software, peer-reviewed conference papers (not posters or presentations), published reports, patents, Master's and PhD theses. -**Do not include** -* Work that was simply inspired by proximity to LTER research. We are concerned that many of our lists include papers that are very tenuously related to LTER projects and this devalues the entire list. So please do not include papers that are not genuinely LTER-related. If the connection is genuine, but unlikely to be obvious to a casual observer, please include a note explaining the connection, in the “note” field. -* Magazine and newspaper articles about LTER research. We have other methods for highlighting and sharing this information. -* Research that preceded the funding of the LTER site. This is very appropriate for you to maintain as reference material on your site websites, but should not be included as a product of the LTER program. -* Personal communications. Again -- great for your site record, but not needed for the Network record. -* Abstracts for conference presentations or posters. These are legitimate products, but in the context of a 40-year program, they are relatively ephemeral, and make it look like we are inflating our numbers. -* Unpublished work - this only creates more duplicates that need to be resolved. +### Do not include -## Bibtex updates -Zotero is becoming the most common system for maintaining a publication database at LTER sites, but if your site prefers EndNote or a custom database, you may provide your update in the form of a bibtex file. [See instructions](https://lter.github.io/im-manual/bibtex). +- Work that was simply inspired by proximity to LTER research. We are concerned that many of our lists include papers that are very tenuously related to LTER projects and this devalues the entire list. So please do not include papers that are not genuinely LTER-related. If the connection is genuine, but unlikely to be obvious to a casual observer, please include a note explaining the connection, in the "note" field. +- Magazine and newspaper articles about LTER research. We have other methods for highlighting and sharing this information. +- Research that preceded the funding of the LTER site. This is very appropriate for you to maintain as reference material on your site websites, but should not be included as a product of the LTER program. +- Personal communications. Again--great for your site record, but not needed for the Network record. +- Abstracts for conference presentations or posters. These are legitimate products, but in the context of a 40-year program, they are relatively ephemeral, and make it look like we are inflating our numbers. +- Unpublished work - this only creates more duplicates that need to be resolved. +::: -## Zotero updates +## Bibtex Updates + +Zotero is becoming the most common system for maintaining a publication database at LTER sites, but if your site prefers EndNote or a custom database, you may provide your update in the form of a bibtex file. See instructions [here](https://lter.github.io/docs-network/im/bibtex.html). + +## Zotero Updates 1. Set up a Zotero account and a group library. 2. Download and install the Zotero desktop client and the browser add-on for the browser of your choice. @@ -34,44 +38,39 @@ Zotero is becoming the most common system for maintaining a publication database 8. **IMPORTANT**: When you do a significant update to your library, let the LNO know and we'll drag the new publications from your library to the Network library and sync them so they appear in the LTER Network bibliography. There is not currently a way to autosync group libraries (which is probably a wise thing). 9. After updating, the LNO will search for and resolve duplicates. The merge process adds all the tags that were associated with either of the duplicate publications to the resulting combined publication. For example: if Andrews Forest, and Harvard Forest each upload the same publication, marked with their own tags (LTER-AND and LTER-HFR), the merged publication will have both tags. This is a quick process for a few publications, but even so, it adds up for hundreds. If you can share with us when your last update occurred, it will help to focus the search. -**Notes on item types** +### Notes on Item Types -Conference “papers” are a particular challenge. Juried conference papers (where a full paper results and is reviewed and published) should be added to Zotero as conference papers. Abstracts of meeting presentations (which don’t appear as papers) should be entered in Zotero under the “presentation” item type. NSF accepts presentations in annual project reports, but the LNO does not include them in the Network bibliography. +Conference "papers" are a particular challenge. Juried conference papers (where a full paper results and is reviewed and published) should be added to Zotero as conference papers. Abstracts of meeting presentations (which don't appear as papers) should be entered in Zotero under the "presentation" item type. NSF accepts presentations in annual project reports, but the LNO does not include them in the Network bibliography. -Find full details on the definition of item types and the required and optional fields on the [biblio-fields](https://lter.github.io/im-manual/biblio-fields) page. +Find full details on the definition of item types and the required and optional fields on the [biblio fields](https://lter.github.io/docs-network/im/biblio-fields.html) page. -## FAQ’s ## +## Frequently Asked Questions (FAQs) -**Q:** Do you have the publications from our most recent annual report? -**A:** The LNO does not receive your annual reports to NSF. The LTER Network Office is not part of NSF and NSF has very strict rules about how they share information. The only way we would receive your annual report is if you send it to us. +- **Q:** Do you have the publications from our most recent annual report? + - **A:** The LNO does not receive your annual reports to NSF. The LTER Network Office is not part of NSF and NSF has very strict rules about how they share information. The only way we would receive your annual report is if you send it to us. -**Q:** Where did you get those most recent papers? -**A:** The LNO has a Web of Science alert set up for all LTER grant numbers in funding acknowledgements. We get 30-50 hits per month on those (for all of LTER) and we add them to our Zotero library (tagged with the appropriate site) when they come in. That's the source of the newer articles. This allows us to keep the Network bibliography reasonably current. Otherwise, we would always be a year or more out of date. +- **Q:** Where did you get those most recent papers? + - **A:** The LNO has a Web of Science alert set up for all LTER grant numbers in funding acknowledgements. We get 30-50 hits per month on those (for all of LTER) and we add them to our Zotero library (tagged with the appropriate site) when they come in. That's the source of the newer articles. This allows us to keep the Network bibliography reasonably current. Otherwise, we would always be a year or more out of date. -**Q:** I see articles without dates or with only partial titles. -**A:** Articles without dates probably were incomplete in the original file we received or they have only been published online (not yet in print) at the time we added them. When they come out in print, we generally receive a second alert, which we merge with the first. +- **Q:** I see articles without dates or with only partial titles. + - **A:** Articles without dates probably were incomplete in the original file we received or they have only been published online (not yet in print) at the time we added them. When they come out in print, we generally receive a second alert, which we merge with the first. -**Q:** Our site uses internal accession numbers to track our publications. Where should that go? -**A:** Many other kinds of information can go in the "Extra" field in Zotero, including accession numbers. You may need to develop a specific export mapping if you maintain your site bibliography in a custom database. +- **Q:** Our site uses internal accession numbers to track our publications. Where should that go? + - **A:** Many other kinds of information can go in the "Extra" field in Zotero, including accession numbers. You may need to develop a specific export mapping if you maintain your site bibliography in a custom database. -**Q:** Is there a way to track data that is associated with a publication? -**A:** Yes! This too can go in the extra field. Be sure to include it on its own line. For additional information, see [BLE's Zotero Javascript Search Client Repo](https://github.com/BLE-LTER/Zotero-JavaScript-Search-Client). +- **Q:** Is there a way to track data that is associated with a publication? + - **A:** Yes! This too can go in the extra field. Be sure to include it on its own line. For additional information, see [BLE's Zotero Javascript Search Client Repo](https://github.com/BLE-LTER/Zotero-JavaScript-Search-Client). -**Q:** I like the LTER Network search client. Can I create something similar for my own site? -**A:** That would be awesome. Find more information at [LTER Network Zotero client Repo](https://github.com/lter/Zotero-JavaScript-Search-Client) and [BLE's Zotero Javascript Search Client Repo](https://github.com/BLE-LTER/Zotero-JavaScript-Search-Client) +- **Q:** I like the LTER Network search client. Can I create something similar for my own site? + - **A:** That would be awesome. Find more information at [LTER Network Zotero client Repo](https://github.com/lter/Zotero-JavaScript-Search-Client) and [BLE's Zotero Javascript Search Client Repo](https://github.com/BLE-LTER/Zotero-JavaScript-Search-Client) -**Q:** What's the point of all this? -**A:** Beyond simply reporting the products of LTER research, combining the LTER Network bibliography allows us to ask and answer questions about how network-wide synthesis happens. At least two big analyses have come out of the LTER Network bibliography: +- **Q:** What's the point of all this? + - **A:** Beyond simply reporting the products of LTER research, combining the LTER Network bibliography allows us to ask and answer questions about how network-wide synthesis happens. At least two big analyses have come out of the LTER Network bibliography + - [Collaboration across Time and Space in the LTER Network](https://doi.org/10.1093/biosci/biaa014). March 2020. Tian-Yuan Huang, Martha R Downs, Jun Ma, Bin Zhao. BioScience, Volume 70, Issue 4, Pages 353–364, doi: 10.1093/biosci/biaa014 + - [Evolution of Collaboration within the US Long Term Ecological Research Network](https://doi.org/10.1525/bio.2010.60.11.9). December 2010. Jeffrey C. Johnson, Robert R. Christian, James W. Brunt, Caleb R. Hickman, Robert B. Waide. BioScience, Volume 60, Issue 11, Pages 931–940, doi: 10.1525/bio.2010.60.11.9 -> [Collaboration across Time and Space in the LTER Network](https://doi.org/10.1093/biosci/biaa014). March 2020. -> Tian-Yuan Huang, Martha R Downs, Jun Ma, Bin Zhao -> BioScience, Volume 70, Issue 4, Pages 353–364, doi: 10.1093/biosci/biaa014 -> -> [Evolution of Collaboration within the US Long Term Ecological Research Network](https://doi.org/10.1525/bio.2010.60.11.9). December 2010. -> Jeffrey C. Johnson, Robert R. Christian, James W. Brunt, Caleb R. Hickman, Robert B. Waide Author Notes -> BioScience, Volume 60, Issue 11, Pages 931–940, doi: 10.1525/bio.2010.60.11.9 +## Acknowledgements -## Acknowledgements ## Many thanks to Tim Whiteaker for developing the search client linked to Zotero; to Tommy Thelan, for customizing it for the LTER Network website; and to all the LTER information managers and administrators who have maintained the database over the years. Thanks, too, to the many creators and maintainers of Zotero, which is developed as a project by the non-profit [Corporation for Digital Scholarship](http://digitalscholar.org/). It was originally created at the [Center for History and New Media](https://en.wikipedia.org/wiki/Center_for_History_and_New_Media) at George Mason University. diff --git a/im/site-websites.qmd b/im/site-websites.qmd index 0478435..e4ab1e4 100644 --- a/im/site-websites.qmd +++ b/im/site-websites.qmd @@ -6,31 +6,27 @@ format: html If you're one of those (un)lucky IMs who handles your LTER site's website, then read on. ## Content + Consistent with LTER's generally bottom-up philosophy, the content and organization of LTER site websites is not determined by the Network Office. Each site has different audiences to prioritize and is situated differently within its home institution (or within a group of institutions and partners). However, maintaining some consistency across sites allows NSF, reviewers, and colleagues to easily find the information that is important to them. To achieve this balance, the network developed and approved a set of [Content Guidelines for LTER websites](https://lternet.edu/?taxonomy=document-types&term=lter-network-branding). Please refer to these guidelines when developing new sites and updating existing websites. ## Platforms -Exactly *how* you go about creating or maintaining your site's website depends on the legacy of the existing website (if any), what resources are available to you at your institution, how much your site has budgeted for website work, and what your site needs from your website. Some of the more common options across sites are listed below, as well as one new and interesting option. + +Exactly _how_ you go about creating or maintaining your site's website depends on the legacy of the existing website (if any), what resources are available to you at your institution, how much your site has budgeted for website work, and what your site needs from your website. Some of the more common options across sites are listed below, as well as one new and interesting option. ### Drupal and DEIMS -[Drupal](https://www.drupal.org/) is an open-source content management system for building and maintaining websites. -Several LTER sites use Drupal, and some of them joined forces to create DEIMS (the Drupal Ecological Information Management System, depending on whom you ask), a Drupal-based website solution which handles functionality common across LTER sites such as data catalog, bibliography, and personnel lists. -DEIMS was developed in Drupal 7 and upgrade instructions to Drupal 8/9 can be found in a [git repository](https://github.com/lter/Deims7-8-Migration). Drupal manages information in a database, and modules have been developed to import and export ecological metadata language (EML) documents. +[Drupal](https://www.drupal.org/) is an open-source content management system for building and maintaining websites. Several LTER sites use Drupal, and some of them joined forces to create DEIMS (the Drupal Ecological Information Management System, depending on whom you ask), a Drupal-based website solution which handles functionality common across LTER sites such as data catalog, bibliography, and personnel lists. + +DEIMS was developed in Drupal 7 and upgrade instructions to Drupal 8/9 can be found in a [GitHub repository](https://github.com/lter/Deims7-8-Migration). Drupal manages information in a database, and modules have been developed to import and export ecological metadata language (EML) documents. Developing a new website in Drupal is more complex than, e.g., WordPress, but offers more opportunities for customization. However, IM supporting developments at EDI and the IMC have been replacing most functionality Drupal has been lauded for. If you already use DEIMS or are familiar with Drupal reach out to the IMs at these sites to learn more: [NTL](https://lter.limnology.wisc.edu/), [KNZ](http://knz.lternet.edu/), [PIE](https://pie-lter.ecosystems.mbl.edu/). ### WordPress -Many sites use WordPress for its ease of migration and editing. -However, a DEIMS-like solution doesn't exist for WordPress, so you will have to find a way to support interactive features such as a data catalog. -Reach out to the IMs at these sites to learn more: [VCR](https://www.vcrlter.virginia.edu/home2/), [CAP](https://sustainability-innovation.asu.edu/caplter/), [JRN](https://lter.jornada.nmsu.edu/). +Many sites use WordPress for its ease of migration and editing. However, a DEIMS-like solution doesn't exist for WordPress, so you will have to find a way to support interactive features such as a data catalog. Reach out to the IMs at these sites to learn more: [VCR](https://www.vcrlter.virginia.edu/home2/), [CAP](https://sustainability-innovation.asu.edu/caplter/), [JRN](https://lter.jornada.nmsu.edu/). ### Static Website -There are many [advantages to static websites](https://blog.squido.org/why-static-html/). -For example, you can typically find a free host for a static website, they're secure, and they can be blazingly fast. -While static websites used to be just for geeks, content management systems are evolving which make the editing experience more similar to WordPress or Drupal. -By harnessing the power of online services and APIs, static sites can include interactive features like data catalogs and bibliographies. -Reach out to the IMs at these sites to learn more: [BLE](https://ble.lternet.edu/), [SBC](https://sbclter.msi.ucsb.edu/). +There are many [advantages to static websites](https://blog.squido.org/why-static-html/). For example, you can typically find a free host for a static website, they're secure, and they can be blazingly fast. While static websites used to be just for geeks, content management systems are evolving which make the editing experience more similar to WordPress or Drupal. By harnessing the power of online services and APIs, static sites can include interactive features like data catalogs and bibliographies. Reach out to the IMs at these sites to learn more: [BLE](https://ble.lternet.edu/), [SBC](https://sbclter.msi.ucsb.edu/). ### DataONE Portal @@ -40,4 +36,3 @@ For a relatively new paid option with simpler sites, you may be interested in [D In other words, you can describe your project on your own portal page, and you can have a complete data catalog as long as all of your datasets are discoverable within DataONE. If you need other fancy features though, you may need to look elsewhere. -