Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
106
datasets available to search
ShareScore release 0.9.0
Dataset results
106 results for “design patterns”
North Temperate Lakes LTER: Crayfish Abundance 1981 - current (Reformatted to the ecocomDP Design Pattern)
This data package is formatted as an ecocomDP (Ecological Community Data Pattern). For more information on ecocomDP see https://github.com/EDIorg/ecocomDP. This Level 1 data package was derived from the Level 0 data package found here: https://pasta.lternet.edu/package/metadata/eml/knb-lter-ntl/3/29. The abstract below was extracted from the Level 0 data package and is included for context: Crayfish data include crayfish catch in cylindrical minnow traps baited with beef liver and occasional occurrence in other gear used to sample fish. Traps are placed at fyke net locations in nine study lakes (Allequash, Big Muskellunge, Crystal, Sparkling, Trout, Mendota, Monona, Wingra and Fish). Crayfish traps have been eliminated as gear in the Madison area lakes (Mendota, Monona, Wingra, and Fish) after 2003. Individuals are identified to species and counted. In Trout and Sparkling Lake more detailed surveys have been conducted during the summer on an ad hoc basis to track distribution and abundance of the invading species Orconectes rusticus. Additional data sets consist of pre-LTER sets (initiated in late June 1972) gathered by Capelli (Ph.D. dissertation) and Lorman (Ph.D. dissertation). Most of pre-LTER data is detailed distribution in Trout Lake, and community composition in other area lakes. Sampling Frequency: annually Number of sites: 9 Note that 2020 data does not exist due to insufficient sampling.
North Temperate Lakes LTER: Benthic Macroinvertebrates 1981 - current (Reformatted to the ecocomDP Design Pattern)
This data package is formatted as an ecocomDP (Ecological Community Data Pattern). For more information on ecocomDP see https://github.com/EDIorg/ecocomDP. This Level 1 data package was derived from the Level 0 data package found here: https://pasta.lternet.edu/package/metadata/eml/knb-lter-ntl/11/35. The abstract below was extracted from the Level 0 data package and is included for context: Macroinvertebrates are collected from selected shoreline and deep water locations in the seven primary lakes (Allequash, Big Muskellunge, Crystal, Sparkling, and Trout lakes, and unnamed lakes 27-02 [Crystal Bog], and 12-15 [Trout Bog]) in the Trout Lake area using modified Hester-Dendy samplers. Samplers are placed at fyke net and gill net locations in August and retrieved 3-4 weeks later. Macroinvertebrates are preserved in ethanol. This dataset contains counts of various groups of macroinvertebrates identified from specific samples. The majority of the identifications are at the genus level. The data table "Benthic Macroinvertebrate Codes" identifies the taxonomic group represented by each group code. Taxonomic references: Ecology and Classification of North American Freshwater Invertebrates, Edited by James H Thorp and Alan P Covich, Academic Press, Inc, 1991; Aquatic Insects of Wisconsin, William L Hilsenhoff, Natural History Museums Council, University of Wisconsin-Madison (1995). Sampling Frequency: annually Number of sites: 7
North Temperate Lakes LTER: Fish Abundance 1981 - current (Reformatted to the ecocomDP Design Pattern)
This data package is formatted as an ecocomDP (Ecological Community Data Pattern). For more information on ecocomDP see https://github.com/EDIorg/ecocomDP. This Level 1 data package was derived from the Level 0 data package found here: https://pasta.lternet.edu/package/metadata/eml/knb-lter-ntl/7/39. The abstract below was extracted from the Level 0 data package and is included for context: This data set is a derived data set based on fish catch data. Data are collected annually to enable us to track the fish assemblages of eleven primary lakes (Allequash, Big Muskellunge, Crystal, Sparkling, Trout, bog lakes 27-02 [Crystal Bog] and 12-15 [Trout Bog], Mendota, Monona, Wingra and Fish). Sampling on Lakes Monona, Wingra, and Fish started in 1995; sampling on other lakes started in 1981. Sampling is done at six littoral zone sites per lake with seine, minnow or crayfish traps, and fyke nets; a boat-mounted electrofishing system samples three littoral transects. Vertically hung gill nets are used to obtain two pelagic samples per lake from the deepest point. A trammel net samples across the thermocline at two sites per lake. In the bog lakes only fyke nets and minnow traps are deployed. Parameters measured include species-level identification and lengths for all fish caught, and weight and scale samples from a subset. Derived data sets include species richness, catch per unit effort, and size distribution by species, lake, and year. Dominant species vary from lake to lake. Perch, rockbass, and bluegill are common, with walleye, large and smallmouth bass, northern pike and muskellunge as major piscivores. Cisco have been present in the pelagic waters of four lakes, and the exotic species, rainbow smelt, is present in two. The bog lakes contain mudminnows. Protocol used to generate data: Day seines were only used in 1981 and have been eliminated from this data set to make sampling effort across years comparable. Number caught for each species is summed over repetitions of
CGR02 Sweep sampling of Grasshoppers on Konza Prairie LTER watersheds (Reformatted to the ecocomDP Design Pattern)
This data package is formatted as an ecocomDP (Ecological Community Data Pattern). For more information on ecocomDP see https://github.com/EDIorg/ecocomDP. This Level 1 data package was derived from the Level 0 data package found here: https://pasta.lternet.edu/package/metadata/eml/knb-lter-knz/29/18. The abstract below was extracted from the Level 0 data package and is included for context: Sweep samples were taken for grasshoppers (Acrididae) at two sites for each of 14 Konza Prairie LTER watersheds. Samples are taken in late July to early August. At each site on each occasion, 10 sets of 20 sweeps (200 sweeps total) are taken. Stored data include for each site on each occasion: total number of each species (all instars combined) collected and total number for each instar for each species (200 sweeps combined).
CSM01 Seasonal Summary of Numbers of Small Mammals on 14 LTER Traplines in Prairie Habitats at Konza Prairie (Reformatted to the ecocomDP Design Pattern)
This data package is formatted as an ecocomDP (Ecological Community Data Pattern). For more information on ecocomDP see https://github.com/EDIorg/ecocomDP. This Level 1 data package was derived from the Level 0 data package found here: https://pasta.lternet.edu/package/metadata/eml/knb-lter-knz/88/8. The abstract below was extracted from the Level 0 data package and is included for context: Data set contains seasonal summaries (spring and autumn) of the number of individuals of each species of small mammal captured (relative abundance) on each grassland trapline. Each record contains year, season, trapline and number of individuals captured of each species. These live trap records are based on daily captures during two 4-day trapping periods in spring (late February to early April) and autumn (early October to mid-November) for each of 14 permanent traplines established on seven fire-grazing treatments (two traplines per treatment). These seven fire-grazing treatments include three sites that are grazed by bison (1 unburned, 1 annual burn and 1 4-year burn) and four sites that are not grazed by bison (1 unburned, 1 annual burn and 2 4-year burn).
[DEPRECATED] CFC01 Kings Creek long-term fish and crayfish community sampling at Konza Prairie (Reformatted to ecocomDP Design Pattern)
This data package has been deprecated due to several issues in the L0 source dataset that prohibits the creation of an L1 ecocomDP dataset. This data package is formatted according to the "ecocomDP", a data package design pattern for ecological community surveys, and data from studies of composition and biodiversity. For more information on the ecocomDP project see https://github.com/EDIorg/ecocomDP/tree/master, or contact EDI https://environmentaldatainitiative.org. This Level 1 data package was derived from the Level 0 data package found here: https://portal.edirepository.org/nis/mapbrowse?scope=knb-lter-knz&identifier=130&revision=4 The abstract below was extracted from the Level 0 data package and is included for context:
Meiobenthos abundance. Long-term variability and dynamics of estuarine meiobenthic populations for North Inlet Estuary, South Carolina, from 1972 to 1992, North Inlet LTER (Reformatted to the ecocomDP Design Pattern)
This data package is formatted as an ecocomDP (Ecological Community Data Pattern). For more information on ecocomDP see https://github.com/EDIorg/ecocomDP. This Level 1 data package was derived from the Level 0 data package found here: https://pasta.lternet.edu/package/metadata/eml/knb-lter-nin/6/1. The abstract below was extracted from the Level 0 data package and is included for context: The original purpose of this research was to determine if natural meiobenthic assemblages exhibited continuity over time and to monitor several physical variables to determine if these influenced long-term temporal patterns. The most recent study focused on variation and the relations of meiobenthos abundance with environmental factors over 11 years. Typically marine benthic community studies are limited temporally and the majority of previously published 'longterm' meiofauna results (all taxa) were based on about a year's duration.
Zooplankton Data for North Inlet Estuary, South Carolina, from 1981 to 1992, North Inlet LTER (Reformatted to the ecocomDP Design Pattern)
This data package is formatted as an ecocomDP (Ecological Community Data Pattern). For more information on ecocomDP see https://github.com/EDIorg/ecocomDP. This Level 1 data package was derived from the Level 0 data package found here: https://pasta.lternet.edu/package/metadata/eml/knb-lter-nin/2/1. The abstract below was extracted from the Level 0 data package and is included for context: This data package consists of Zooplankton Data for North Inlet Estuary, South Carolina, from 1981 to 1992, North Inlet LTER. The purpose of the long term monitoring of zooplankton was to characterize the fauna in the water column larger than or equal to 153 microns and to obtain some basic information on each of the taxa encountered there. A sampling regime of collections made at regular biweekly intervals was implemented to provide the best quantitative assessment of long term changes in the zooplankton population dynamics.
Macrobenthos Sampling data for the North Inlet Estuary, Georgetown,South Carolina, from 1981 to 1992 North Inlet LTER (Reformatted to the ecocomDP Design Pattern)
This data package is formatted as an ecocomDP (Ecological Community Data Pattern). For more information on ecocomDP see https://github.com/EDIorg/ecocomDP. This Level 1 data package was derived from the Level 0 data package found here: https://pasta.lternet.edu/package/metadata/eml/knb-lter-nin/9/1. The abstract below was extracted from the Level 0 data package and is included for context: This data package consists of Macrobenthos Sampling Data for North Inlet Stations Bread and Butter Creek from 1981 to 1992, and Debidue Creek from 1981 to 1984, North Inlet LTER. The purpose of this study was to document the composition and abundance of macrobenthic subtidal populations over time at one mud and one sand site. Macrobenthos was defined here as those animals retained on a 0.5 mm mesh screen.
LTER Epibenthos Sampling Data for North Inlet Estuary, Georgetown, South Carolina from 1981 to 1992, North Inlet LTER (Reformatted to the ecocomDP Design Pattern)
This data package is formatted as an ecocomDP (Ecological Community Data Pattern). For more information on ecocomDP see https://github.com/EDIorg/ecocomDP. This Level 1 data package was derived from the Level 0 data package found here: https://pasta.lternet.edu/package/metadata/eml/knb-lter-nin/7/1. The abstract below was extracted from the Level 0 data package and is included for context: This data package consists of Epibenthos Sampling for North Inlet Stations Bread and Butter Creek, from 1981 to 1992, and Debidue Creek from 1981 to 1984, The purpose of the long term monitoring of Epibenthos was to determine seasonal and inter-annual changes in the taxonomic/life stage composition and abundance of small motile epibenthic invertebrates and fishes (1-20 mm in length) in the major sub- tidal habitats of North Inlet estuary.
Long Term Mammal Data from Powdermill Biological Station 1979-1999 (Reformatted to the ecocomDP Design Pattern)
This data package is formatted as an ecocomDP (Ecological Community Data Pattern). For more information on ecocomDP see https://github.com/EDIorg/ecocomDP. This Level 1 data package was derived from the Level 0 data package found here: https://pasta.lternet.edu/package/metadata/eml/knb-lter-vcr/67/20. The abstract below was extracted from the Level 0 data package and is included for context: This is a 20-year record of small mammal trapping from the Powdermill Biological Station, Rector, PA 15677 collected by Joseph F. Merritt. It is included here as a comparative source of small mammal data.
Experimental package for "Live Software Documentation of Design Pattern Instances"
Experimental package containing the materials and data for an empirical study conducted with the DesignPatterDoc plugin for IntelliJ IDEA.
Dataset for "Designing Microservice Systems Using Patterns: An Empirical Study on Quality Trade-Offs"
<p>This package provides all published resources used and produced in the context of the research study leading to the article <em>"Designing Microservice Systems Using Patterns: An Empirical Study on Quality Trade-Offs"</em>, presented in ICSA 2022's technical track.</p>
BRAIN Journal-Two new software behavioral design patterns: Obligation Link and History Reminder-Figure 5. The Sequence Diagram of the "History Reminder" design pattern
<p>Analyzing the two main classes HistoryReminder and HistoryReminderOriginator of the “History Reminder” design pattern, we find that these two classes act as actors of the whole sequence of operations. The sequence diagram of the “History Reminder” design pattern is given below in Figure 5.</p>
BRAIN Journal-Two new software behavioral design patterns: Obligation Link and History Reminder-Figure 4. The Flow chart of the "History Reminder" design pattern
<p>The “History Reminder” design pattern has two main classes: HistoryReminder and HistoryReminderOriginator. The flow chart of the “History Reminder” design pattern is given in Figure 4.</p>
BRAIN Journal-Two new software behavioral design patterns: Obligation Link and History Reminder-Figure 3. The class diagram of the "History Reminder" design pattern
<p>The “History Reminder” design pattern consists of two basic classes. The first one is the HistoryReminder class and the second one is HistoryReminderOriginator class. Here, we have removed the Caretaker class which has been used to restore and save the memento state in the case of the traditional well-known Memento design pattern. The Caretaker object’s responsibility has been passed to the HistoryReminder object itself. It saves and restores the object within itself and returns it to the HistoryReminderOriginator object. The class diagram of the HistoryReminder design pattern is given below in Figure 3.</p>
BRAIN Journal-Two new software behavioral design patterns: Obligation Link and History Reminder-Figure 2. The class diagram of the "Obligation Link" design pattern
<p>Here is the structure of the “Obligation Link” design pattern described through another UML concept, called class diagrams. Contrary to the sequence diagrams which describe the behaviour, class diagrams specify static structural information about a program. The important information for a class, such as its attribute, operation, etc, along with relationship between classes can be specified using a class diagram</p>
BRAIN Journal-Two new software behavioral design patterns: Obligation Link and History Reminder-Figure 1. The sequence diagram of the "Obligation Link" design pattern
<p>A sequence diagram is used to model the flow of the logic of the system. A sequence diagram represents perhaps the most popular Unified Modelling Language (UML) diagram that describes the behavior of a scheme. Figure 1 shows the sequence diagram of “Obligation Link” design pattern.</p>
On understanding and manipulating the hatching patterns of Diabrotica v. virgifera (Coleoptera: Chrysomelidae) eggs to improve the design of experiments
<p><em>Diabrotica v. virgifera </em>(Coleoptera: Chrysomelidae) is a well-studied pest of maize in North America and Europe. Many studies on its biology, behaviour or management rely individuals reared from either field-collected insect or on laboratory colonies. Naturally, <em>D. v. virgifera</em> eggs require an obligate diapause which can cause technical challenges such as a deceleration of research activities. To allow better planning of experimentation, we have investigated the survival and temporal hatching patterns of the pest`s eggs depending on diapause length as well as on post-diapause incubation temperature. Several series of laboratory assays revealed that eggs from diapausing populations hatch at highest rates and with most synchronized hatching start and peaks when overwintered at natural diapause length of eight to ten months or shorter down to five months (20 to 24 °C incubation temperatures). Comparably good hatching rates were found in eggs diapaused for only two months, but hatching patterns appeared more spread and variable. Diapause shorter than two months or longer than ten months reduced hatching successes, as did low incubation temperatures. Data matrices on egg overwintering survival, on the beginning, peak, duration and termination of egg hatching, as well as on hatching rates are provided for different diapause lengths and incubation temperatures of diapausing and, as a comparison, non-diapausing <em>D. v. virigifera</em> to support scientists choosing a colony which fits best their experimental setup and study conditions, as well as to properly plan such studies.</p>
Empirical Study of the Relationship between Design Patterns and Code Smells
<p>Software systems are often developed in such a way that good practices in the object-oriented paradigm are not met, causing the occurrence of specific disharmonies which are sometimes called code smells. Design patterns catalogue best practices for developing object-oriented software systems. Although code smells and design patterns are widely divergent, there might be a co-occurrence relation between them. The objective of this paper is to empirically evaluate if the presence of design patterns is related to the presence of code smells at different granularity levels. We performed an empirical replication study using 20 design patterns and 13 code smells in ten small-size to medium-size, open-source Java-based systems. We applied statistical analysis and association rules. Results confirm that classes participating in design patterns have less smell-proneness and smell frequency than classes not participating in design patterns. We also noticed that every design pattern category act in the same way in terms of smell-proneness in the subject systems. However, we observed, based on the association rules learning and the proposed validation technique, that some patterns may be linked with certain smells in some cases. For instance, Command patterns can co-occur with God Class, Blob and External Duplication smell.</p> <p><strong>The published data set contains the following:</strong></p> <ol> <li>List of the selected systems (source code files)</li> <li>The P-MARt: the design pattern repository as XML for the selected systems. </li> <li>Data of design patterns and code smells: We processed this data by parsing the design pattern XML file and running the smell detection tool (inFusion).</li> <li>The data of the data mining analysis.</li> </ol>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.