You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: materials/sections/adc-creating-data-portals.qmd
+40-37Lines changed: 40 additions & 37 deletions
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ To see an example of a portal, please view the [Toolik Field Station's portal](h
20
20
21
21
## Portal Features
22
22
23
-
Published portals vary in their design according to the needs and preferences of the individual or group. However, when constructing a portal there are three core elements: a data page, a metrics page, and customizable free-form pages.
23
+
Published portals vary in their design according to the needs and preferences of the individual or group. However, when constructing a portal there are three core elements: a data page, a metrics page, and customizable free-form pages.
24
24
25
25
### Flexible Content Creation {.unnumbered}
26
26
@@ -32,7 +32,7 @@ Portals can be constructed as a website providing information about the research
32
32
33
33
### Curated Collections of Data {.unnumbered}
34
34
35
-
The data page is arguably the most important component of the Arctic Data Center portal system. This is where users will display the data packages of their choice. Whether these data reflect research products from your research group (collated based on contributor IDs), or thematic areas of research interest (collated based on keyword and search terms), will depend upon the intended use of the portal but in all cases, you are refining the suite of data viewed by your audience. The data page looks and performs just like the main Arctic Data Center catalog - with some added bonuses, see below.
35
+
The data page is arguably the most important component of the Arctic Data Center portal system. This is where users will display the data packages of their choice. Whether these data reflect research products from your research group (collated based on contributor IDs), or thematic areas of research interest (collated based on keyword and search terms), will depend upon the intended use of the portal but in all cases, you are refining the suite of data viewed by your audience. The data page looks and performs just like the main Arctic Data Center catalog - with some added bonuses, see below.
The Arctic Data Center has also developed custom features for data portals. For example, [this video](https://drive.google.com/file/d/1cwStXzB4ZMaTJqh3U-sI5nOSVJtrjkNH/view?usp=sharing) demonstrates a custom portal map page on the Permafrost Discovery Gateway, showing how datasets, like retrogressive thaw slump measurements, can be explored interactively. Users can zoom, pan, and filter visible data layers.
50
+
51
+
This [example](https://drive.google.com/file/d/1ID4HflHeKSUZ8JuQcYNYUQBifiHTALIS/view?usp=sharing) from the Salmon Knowledge Portal highlights how Shiny Apps can make data portals interactive and user-friendly. By embedding Shiny Apps directly within a portal page, users can explore datasets in real-time, filter information, and visualize patterns.
52
+
53
+
Interested in adding interactivity to your data portal? Reach out to our data curation team to get started: [support\@arcticdata.io](mailto::support@arcticdata.io)
54
+
47
55
### Metrics, Metrics, Metrics {.unnumbered}
48
56
49
-
As with the full Arctic Data Center catalog, we aggregate metrics for the collection of data packages within a portal. This page is not customizable - it comes as a default with the portal - but you can choose to delete it. The metrics provided include a summary of the holdings: number, volume, time period, format of datasets, metadata assessment scores, citations across all packages, and counts of downloads and views. These latter metrics can be particularly useful if wanting to track the usage or reach of your project or group's activities.
57
+
As with the full Arctic Data Center catalog, we aggregate metrics for the collection of data packages within a portal. This page is not customizable - it comes as a default with the portal - but you can choose to delete it. The metrics provided include a summary of the holdings: number, volume, time period, format of datasets, metadata assessment scores, citations across all packages, and counts of downloads and views. These latter metrics can be particularly useful if wanting to track the usage or reach of your project or group's activities.
## Enhancing Access to Social Science Research Data
55
62
56
-
Many of the portal examples provided above are organizational, individual or project portals created by members of the Arctic research community. The ability to group relevant datasets and customize search criteria increases data discoverability and accessibility among target audiences. The Arctic Data Center has leveraged these features to create a specific portal for social science data.
63
+
Many of the portal examples provided above are organizational, individual or project portals created by members of the Arctic research community. The ability to group relevant datasets and customize search criteria increases data discoverability and accessibility among target audiences. The Arctic Data Center has leveraged these features to create a specific portal for social science data.
57
64
58
65
59
66
60
-
Within this portal, users can subset by social science [discipline](https://raw.githubusercontent.com/NCEAS/adc-disciplines/main/adc-disciplines.png), data type and other metadata fields built into the portal. These search features depend on sufficient user contributed metadata describing the dataset, and as can be seen from the 'with data' toggle, the portal does not require the data themselves to be uploaded to the Arctic Data Center.
67
+
Within this portal, users can subset by social science [discipline](https://raw.githubusercontent.com/NCEAS/adc-disciplines/main/adc-disciplines.png), data type and other metadata fields built into the portal. These search features depend on sufficient user contributed metadata describing the dataset, and as can be seen from the 'with data' toggle, the portal does not require the data themselves to be uploaded to the Arctic Data Center.
61
68
62
69
63
70
64
-
65
-
## Relationship between Arctic Data Center portals and DataONE
71
+
## Relationship between Arctic Data Center portals and DataONE
66
72
67
73
Both DataONE and the Arctic Data Center use Metacat and MetacatUI software and both have the capability for individuals and groups to develop portals. This is true of other repositories running this software. The difference between a portal at the Arctic Data Center and one through DataONE is the corpus of data that can be pulled into your portal. Arctic Data Center portals expose only data held in the Arctic Data Center repository. A portal in DataONE can expose data from across the full network of data repositories - including DataONE. This is particularly useful for interdisciplinary research projects, labs that have published data to multiple repositories etc. However, unlike at the Arctic Data Center, there is a cost associated with a DataONE portal as they are part of the organizations sustainability model.
68
74
69
-
70
75
## Creating Portals
71
76
72
77
A step-by-step guide on how to navigate the Arctic Data Center and create a new portal. For video tutorials on how to create your first portal, please visit the [Arctic Data Center's](https://arcticdata.io/data-portals/#instructional-videos-identifier) website.
@@ -77,7 +82,7 @@ If you are on the [Arctic Data Center's primary website](http://arcticdata.io/),
- Identify a short name for your portal that will become part of the URL. If the name is available, a label will indicate it's available and if the name is taken already, it will note that the name is already taken. This feature ensures the portals are unique.
96
-
- Portal description
97
-
- Sharing options
98
-
- For the purposes of this training, please leave your portal in 'Private' status. You are welcome to return and make the portal public when the portal is complete and is useful to you and others.
99
-
- Permissions
100
-
- Adding collaborators to help you create your portal is as straightforward as copying and pasting in their ORCID into the box below the permissions section. You can choose whether the collaborator can view, edit, or is an owner of the portal. You can have multiples of each role.
101
-
- Partner Logos
99
+
-Portal URL
100
+
-Identify a short name for your portal that will become part of the URL. If the name is available, a label will indicate it's available and if the name is taken already, it will note that the name is already taken. This feature ensures the portals are unique.
101
+
-Portal description
102
+
-Sharing options
103
+
-For the purposes of this training, please leave your portal in 'Private' status. You are welcome to return and make the portal public when the portal is complete and is useful to you and others.
104
+
-Permissions
105
+
-Adding collaborators to help you create your portal is as straightforward as copying and pasting in their ORCID into the box below the permissions section. You can choose whether the collaborator can view, edit, or is an owner of the portal. You can have multiples of each role.
We're going to start with the second section: Adding data to your collection.
119
+
 We're going to start with the second section: Adding data to your collection.
116
120
117
-
When adding data to your collection, you can include any of the datasets that are available at the Arctic Data Center. You build rules based on metadata to define which datasets should be included. Of course, where metadata is incomplete or abbreviated, this will impact your results. Data added to the network in the future that match these rules will also be added to your collection.
121
+
When adding data to your collection, you can include any of the datasets that are available at the Arctic Data Center. You build rules based on metadata to define which datasets should be included. Of course, where metadata is incomplete or abbreviated, this will impact your results. Data added to the network in the future that match these rules will also be added to your collection.
118
122
119
123
The first thing we notice is the ability to include/exclude data based on all/any metadata criteria. This setting applies across all rules.
120
124
121
-
In the default view, you have the starting point for a single rule, and a view showing 0 datasets.
125
+
In the default view, you have the starting point for a single rule, and a view showing 0 datasets.
### Building Search Options for Your Audience{.unnumbered}
137
+
### Building Search Options for Your Audience{.unnumbered}
134
138
135
139
This section covers the first part of the 'data' page: "Add filters to help people find data within your collection". Although it appears first, I recommend constructing these filters after you have defined your data, as you will have a better understanding of the metadata fields that are relevant to your portal collection. It appears at the top of this editor page, as when published, it will be at the top for users. Hence, the editor page reflects the layout of the published page.
136
140
137
-
When selecting "add a search filter" you will be presented with a pop-up that comprises three primary elements:
141
+
When selecting "add a search filter" you will be presented with a pop-up that comprises three primary elements:
138
142
139
-
1. The metadata filed you will be querying
140
-
2. The way in which you want the user to interact with that metadata
141
-
3. Language settings for the filter you are building
143
+
1.The metadata filed you will be querying
144
+
2.The way in which you want the user to interact with that metadata
145
+
3.Language settings for the filter you are building
As you select options for number 1 - the metadata field, the pop-up will refresh to show only those relevant options. Save this filter to close the pop-up, return to the main editor and add another search filter.
149
+
As you select options for number 1 - the metadata field, the pop-up will refresh to show only those relevant options. Save this filter to close the pop-up, return to the main editor and add another search filter.
To watch a tutorial on creating a new freeform page see this video:[Creating a Freeform Text Page](https://arcticdata.io/data-portals/#instructional-videos-identifier)
161
164
@@ -177,7 +180,7 @@ Please see these additional resources for help with markdown:
Copy file name to clipboardExpand all lines: materials/sections/adc-intro-to-policies.qmd
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ We’re best known in the research community as a data archive – researchers u
18
18
19
19
NSF has long had a commitment to data reuse and sharing. Since our start in 2016, we’ve grown substantially – from that original 4 TB of data from ACADIS to now over 300 TB at the start of 2026. In 2021 alone, we saw 16% growth in dataset count, and about 30% growth in data volume. This increase has come from advances in tools – both ours and of the scientific community, plus active community outreach and a strong culture of data preservation from NSF and from researchers. We plan to add more storage capacity in the coming months, as researchers are coming to us with datasets in the terabytes, and we’re excited to preserve these research products in our archive. We’re projecting our growth to be around several hundred TB this year, which has a big impact on processing time. Give us a heads up if you’re planning on having larger submissions so that we can work with you and be prepared for a large influx of data.
20
20
21
-
The data that we have in the Arctic Data Center comes from a wide variety of disciplines. These different programs within NSF all have different focuses – the Arctic Observing Network supports scientific and community-based observations of biodiversity, ecosystems, human societies, land, ice, marine and freshwater systems, and the atmosphere as well as their social, natural, and/or physical environments, so that encompasses a lot right there in just that one program. We’re also working on a way right now to classify the datasets by discipline, so keep an eye out for that coming soon.
[guidelines](https://arcticdata.io/data-ethics/) on how to write and
758
758
what to include in an Ethical Research Practices Statement.
759
759
760
+
## Research Data Publishing Ethics
761
+
762
+
For over 20 years, the [Committee on Publication Ethics (COPE)](https://publicationethics.org/) has provided trusted guidance on ethical practices for scholarly publishing.
763
+
The COPE guidelines have been broadly adopted by academic publishers across disciplines, and represent a common approach to identify, classify, and adjudicate potential breaches of ethics in publication such as authorship conflicts, peer review manipulation, and falsified findings, among many other areas.
764
+
Despite these guidelines, there has been a lack of ethics standards, guidelines, or recommendations for data publications, even while some groups have begun to evaluate and act upon reported issues in data publication ethics.
To address this gap, the [Force 11 Working Group on Research Data Publishing Ethics](https://force11.org/groups/research-data-publishing-ethics/home/) was formed as a collaboration among research data professionals and the Committee on Publication Ethics (COPE) "to develop industry-leading guidance and recommended best practices to support repositories, journal publishers, and institutions in handling the ethical responsibilities associated with publishing research data." The group released the "Joint FORCE11 & COPE Research Data Publishing Ethics Working Group Recommendations" [@puebla_2021], which outlines recommendations for four categories of potential data ethics issues:
769
+
770
+
-[Authorship and Contribution Conflicts](https://zenodo.org/record/5391293/files/Authorship%20%26%20Contributions_datapubethics.pdf?download=1)
771
+
- Authorship omissions
772
+
- Authorship ordering changes / conflicts
773
+
- Institutional investigation of author finds misconduct
- Breaches of contract law governing data redistribution
780
+
-[Risks of publication or release](https://zenodo.org/record/5391293/files/Risk_datapubethics.pdf?download=1)
781
+
- Risks to human subjects
782
+
- Lack of consent
783
+
- Breaches of himan rights
784
+
- Release of personally identifiable information (PII)
785
+
- Risks to species, ecosystems, historical sites
786
+
- Locations of endangered species or historical sites
787
+
- Risks to communities or societies
788
+
- Data harvested for profit or surveillance
789
+
- Breaches of data sovereignty
790
+
-[Rigor of published data](https://zenodo.org/record/5391293/files/Rigor_datapubethics.pdf?download=1)
791
+
- Unintentional errors in collection, calculation, display
792
+
- Un-interpretable data due to lack of adequate documentation
793
+
- Errors of of study design and inference
794
+
- Data manipulation or fabrication
795
+
796
+
Guidelines cover what actions need to be taken, depending on whether the data are already published or not, as well as who should be involved in decisions, who should be notified of actions, and when the public should be notified.
797
+
The group has also published templates for use by publishers and repositories to announce the extent to which they plan to conform to the data ethics guidelines.
798
+
799
+
800
+
760
801
## Exercise: Evaluate a Data Package on the ADC Repository
761
802
762
803
Explore data packages published on the ADC assess the quality of their
0 commit comments