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.
672
datasets available to search
ShareScore release 0.9.0
Dataset results
672 results for “Log”
ODP Leg 199, Hole 1218A - Well Logging Data
<p>Logging data are measurements of physical properties of the formation surrounding a borehole, acquired in situ after completion of coring (wireline logging) or during drilling (Logging-While-Drilling, LWD). The range of data (resistivity, gamma radiation, velocity, density, borehole images,…) in any hole depends on the scientific objectives and operational constraints.</p>
IODP Expedition 302, Hole M0004B - Well Logging Data
<p>Logging data are measurements of physical properties of the formation surrounding a borehole, acquired in situ after completion of coring (wireline logging) or during drilling (Logging-While-Drilling, LWD). The range of data (resistivity, gamma radiation, velocity, density, borehole images,…) in any hole depends on the scientific objectives and operational constraints.</p>
ODP Leg 209, Hole 1272A - Well Logging Data
<p>Logging data are measurements of physical properties of the formation surrounding a borehole, acquired in situ after completion of coring (wireline logging) or during drilling (Logging-While-Drilling, LWD). The range of data (resistivity, gamma radiation, velocity, density, borehole images,…) in any hole depends on the scientific objectives and operational constraints.</p>
ODP Leg 202, Hole 1239A - Well Logging Data
<p>Logging data are measurements of physical properties of the formation surrounding a borehole, acquired in situ after completion of coring (wireline logging) or during drilling (Logging-While-Drilling, LWD). The range of data (resistivity, gamma radiation, velocity, density, borehole images,…) in any hole depends on the scientific objectives and operational constraints.</p>
Cloud-based User Entity Behavior Analytics Log Data Set
<p>This respository contains the CLUE-LDS (CLoud-based User Entity behavior analytics Log Data Set). The data set contains log events from real users utilizing a cloud storage suitable for User Entity Behavior Analytics (UEBA). Events include logins, file accesses, link shares, config changes, etc. The data set contains around 50 million events generated by more than 5000 distinct users in more than five years (2017-07-07 to 2022-09-29 or 1910 days). The data set is complete except for 109 events missing on 2021-04-22, 2021-08-20, and 2021-09-05 due to database failure. The unpacked file size is around 14.5 GB. A detailed analysis of the data set is provided in [1].</p><p>The logs are provided in JSON format with the following attributes in the first level:</p><ul><li><strong>id</strong>: Unique log line identifier that starts at 1 and increases incrementally, e.g., 1.</li><li><strong>time</strong>: Time stamp of the event in ISO format, e.g., 2021-01-01T00:00:02Z.</li><li><strong>uid</strong>: Unique anonymized identifier for the user generating the event, e.g., old-pink-crane-sharedealer.</li><li><strong>uidType</strong>: Specifier for uid, which is either the user name or IP address for logged out users.</li><li><strong>type</strong>: The action carried out by the user, e.g., file_accessed.</li><li><strong>params</strong>: Additional event parameters (e.g., paths, groups) stored in a nested dictionary.</li><li><strong>isLocalIP</strong>: Optional flag for event origin, which is either internal (true) or external (false).</li><li><strong>role</strong>: Optional user role: consulting, administration, management, sales, technical, or external.</li><li><strong>location</strong>: Optional IP-based geolocation of event origin, including city, country, longitude, latitude, etc.</li></ul><p>In the following data sample, the first object depicts a successful user login (see <i>type: login_successful</i>) and the second object depicts a file access (see <i>type: file_accessed</i>) from a remote location:</p><blockquote><p>{"params": {"user": "intact-gray-marlin-trademarkagent"}, "type": "login_successful", "time": "2019-11-14T11:26:43Z", "uid": "intact-gray-marlin-trademarkagent", "id": 21567530, "uidType": "name"}</p><p> {"isLocalIP": false, "params": {"path": "/proud-copper-orangutan-artexer/doubtful-plum-ptarmigan-merchant/insufficient-amaranth-earthworm-qualitycontroller/curious-silver-galliform-tradingstandards/incredible-indigo-octopus-printfinisher/wicked-bronze-sloth-claimsmanager/frantic-aquamarine-horse-cleric"}, "type": "file_accessed", "time": "2019-11-14T11:26:51Z", "uid": "graceful-olive-spoonbill-careersofficer", "id": 21567531, "location": {"countryCode": "AT", "countryName": "Austria", "region": "4", "city": "Gmunden", "latitude": 47.915, "longitude": 13.7959, "timezone": "Europe/Vienna", "postalCode": "4810", "metroCode": null, "regionName": "Upper Austria", "isInEuropeanUnion": true, "continent": "Europe", "accuracyRadius": 50}, "uidType": "ipaddress"}</p></blockquote><p>The data set was generated at the premises of <a href="https://www.huemer-group.com/">Huemer Group</a>, a midsize IT service provider located in Vienna, Austria. Huemer Group offers a range of Infrastructure-as-a-Service solutions for enterprises, including cloud computing and storage. In particular, their cloud storage solution called <a href="https://www.huemer-group.com/hbox/">hBOX</a> enables customers to upload their data, synchronize them with multiple devices, share files with others, create versions and backups of their documents, collaborate with team members in shared data spaces, and query the stored documents using search terms. The hBOX extends the open-source project <a href="https://nextcloud.com">Nextcloud</a> with interfaces and functionalities tailored to the requirements of customers.</p><p>The data set comprises only normal user behavior, but can be used to evaluate anomaly detection approaches by simulating account hijacking. We provide an implementation for identifying similar users, switching pairs of users to simulate changes of behavior patterns, and a sample detection approach in our <a href="https://github.com/ait-aecid/clue-lds">github repo</a>.</p><p>Acknowledgements: Partially funded by the FFG project DECEPT (873980). The authors thank Walter Huemer, Oskar Kruschitz, Kevin Truckenthanner, and Christian Aigner from Huemer Group for supporting the collection of the data set.</p><p><strong>If you use the dataset, please cite the following publication:</strong></p><p>[1] M. Landauer, F. Skopik, G. Höld, and M. Wurzenberger. <a href="https://doi.org/10.1109/BigData55660.2022.10020672">"A User and Entity Behavior Analytics Log Data Set for Anomaly Detection in Cloud Computing"</a>. <a href="http://bigdataieee.org/BigData2022/"><i>2022 IEEE International Conference on Big Data - 6th International Workshop on Big Data Analytics for Cyber Intelligence and Defense (BDA4CID 2022)</i></a>, December 17-20, 2022, Osaka, Japan. IEEE. [<a href="https://www.skopik.at/ait/2022_bigdata.pdf">PDF</a>]</p>
Log Boat - Loch Glashan
Part of a Log Boat found associated with a Crannog (an artificial island settlement) which was excavated in the early 1960's at Loch Glashan, Argyll & Bute (near Lochgilphead). The Crannog was in use throughout much of the 1st millennium AD though recent dating evidence shows that the log boat was associated with the earliest period of occupation at the crannog. The Log Boat is currently on display at the Kelvingrove Art Gallery https://www.glasgowlife.org.uk/museums/venues/kelvingrove-art-gallery-and-museum More information on the Loch Glashan Crannog on Canmore https://canmore.org.uk/site/40047/loch-glashan Source: Objaverse 1.0 / Sketchfab
OOOP Litho Log 002aus21 00A
Ein Auszug aus dem digitalen Findbuch 2021 Wir arbeiten eifrig am Aufbau unseres 4D Kataloges zur digitalen Dokumentation unserer Forschungsobjekte [](http://) Source: Objaverse 1.0 / Sketchfab
UI Logs for Screenshot and for Activity Identification
<p>These data correspond to the set of Problems used for the evaluation of the proposal <strong><em>From Screenshots to Process Models: Improving Activity Identification through Screen Text.</em></strong></p> <p>Each problem includes a User-Interaction (UI) Log that contains comprehensive process information. Accompanying the UI Log are directories with 58 screenshots from different instances of processes recorded on Odoo or Gmail interfaces and directories containing all on-screen text extracted from each screenshot using OCR. The UI Log references the screenshots and their corresponding OCR files for each row.</p> <p>Additionally, results for every execution run per Problem are available. The results directories include subdirectories, differentiated by the image/text weight in the execution, containing the expanded base UI Log with columns resulting from feature extraction and clustering. Each Problem has its summary file, providing an overview of all executions and the relevant clustering and evaluation metrics.</p> <p>A precise breakdown and description of each of the directories and files present in this assessment is provided below:</p> <p><strong>input/Problem_X-Y/ </strong>(where X represents the number of the Problem given in the article and Y its full name).</p> <ul> <li><strong>screenshots/:</strong> contains the screenshots from Odoo and Gmail interfaces. The naming pattern is <em>X_img.png</em> where X is the corresponding identifier. Each record contains up to 58 screenshots representing different activities within the instantiation of a business process.</li> <li><strong>ocr_results/:</strong> stores the results of applying OCR techniques to all screenshots for extracting all on-screen text. This directory includes a .txt file for each image, containing the extracted text. The naming pattern is similar to the previous one: <em>X_ocr.txt </em>where X is the identifier. These files are used for executions that use all on-screen text as a source along with the images.</li> <li><strong>log.csv:</strong> .csv file representing the UI Log of the process. It contains the following columns: <ul> <li><strong>id:</strong> identifier corresponding to a screenshot within the UI log.</li> <li><strong>screenshot:</strong> path to the image corresponding to the row in the UI log within <em>screenshots/.</em></li> <li><strong>timestamp:</strong> time marker for defining the sequential order of actions in the UI log</li> <li><strong>header:</strong> text string extracted from the browser’s tab.</li> <li><strong>header_txt:</strong> path to each corresponding text file within <em>ocr_results/.</em></li> <li><strong>ground_truth:</strong> label assigned to identify and group images by activity. Compared with the <em>activity_label</em> column after algorithm application to determine execution’s evaluation metrics.</li> </ul> </li> </ul> <p><strong>output/X_Y/ </strong>(where X represents an abbreviation of the Problem chosen for execution and Y specifies whether all on-screen text, browser’s tab text or image hash was used).</p> <ul> <li><strong>X_Y_a_b/</strong> (where a,b refers to image/text weight for each execution). Each directory represents one specific execution from a Problem. <ul> <li><strong>df.csv:</strong> .csv file representing the expanded UI Log with the experimentation results after the algorithm has been applied. The new columns are described below: <ul> <li><strong>combined_features:</strong> contains the features extracted per image, either individually using hash or CLIP, or, in the latter case, combining them with those from the text source used.</li> <li><strong>activity_label:</strong> represents the group assigned by the algorithm through clustering based on feature comparison.</li> <li><strong>mapped_prediction:</strong> mapping of the cluster assigned by the algorithm to the group distribution established manually by <em>ground_truth.</em></li> </ul> </li> <li><strong>summary.csv: </strong>file which contains a summary of all executions from a Problem. It contains the following information: <ul> <li><strong>exec:</strong> number indicating the row identifier.</li> <li><strong>image_weight:</strong> parameter that determines the importance of image features in the model.</li> <li><strong>text_weight:</strong> parameter that determines the importance of text features in the model.</li> <li><strong>Evaluation metrics:</strong> <ul> <li><strong>Precision:</strong> the ratio of true positives to the sum of true positives and false positives. It measures the accuracy of not labeling different activities as the same.</li> <li><strong>Recall:</strong> the ratio of true positives to the sum of true positives and false negatives. It measures the ability to identify all the activities properly grouped.</li> <li><strong>F1-Score:</strong> a harmonic mean of precision and recall. It balances the relative contribution of precision and recall equally.</li> </ul> </li> <li><strong>Clustering related metrics. </strong>(Calculated for testing purposes; in the article, our approach focuses solely on evaluation metrics). <ul> <li><strong>Silhoutte Coefficient:</strong> measures how similar is an object to its cluster compared to other clusters. Values range from -1 to 1, with higher values indicating better-defined clusters.</li> <li><strong>Davies-Bouldin Index:</strong> assesses cluster quality by comparing the distance between clusters to the size of the clusters themselves. Lower values indicate better-defined clusters.</li> <li><strong>Calinski-Harabasz Index:</strong> evaluate cluster quality by comparing the spread within clusters to the spread between clusters. Higher values mean better-defined clusters.</li> </ul> </li> </ul> </li> </ul> </li> </ul>
Clausal Congruence Closure Paper Logs, Plots and Tables
<p>These are the log files and other experimental data of our paper on clausal<br>congruence closure together with generated plots and tables.</p>
Classification of African ground pangolin behaviour based on accelerometer readouts: validation of bio-logging methods
<p>Data and R Scripts for the manuscript titled "Classification of African ground pangolin behaviour based on accelerometer readouts: validation of bio-logging methods".</p> <p>Code is for labelling accelerometer data and running a random forest model.<br>Script01. Label the accelerometer data with behavioural labels from BORIS<br>Script02. Create summary metrics and resample frequencies. This includes code adapted from (Clark, 2019; Clark et al., 2022). https://ore.exeter.ac.uk/repository/handle/10871/120152, https://www.int-res.com/abstracts/meps/v701/p145-157/<br>Script03. Run random forest for each frequency and smoothing window.</p> <p>AccelerometerData.zip containes Files grouped by individual. For each individual there is:</p> <p>Accelerometer_data: Accelerometer data.</p> <p>ID: BORIS behaviour output</p> <p>ID_labs: Labelled accelerometer data</p>
IODP Expedition 397, Hole U1587C - Well Logging Data
Logging data are measurements of physical properties of the formation surrounding a borehole, acquired in situ after completion of coring (wireline logging) or during drilling (Logging-While-Drilling, LWD). The range of data (resistivity, gamma radiation, velocity, density, borehole images,…) in any hole depends on the scientific objectives and operational constraints.
IODP Expedition 398, Hole U1589C - Well Logging Data
Logging data are measurements of physical properties of the formation surrounding a borehole, acquired in situ after completion of coring (wireline logging) or during drilling (Logging-While-Drilling, LWD). The range of data (resistivity, gamma radiation, velocity, density, borehole images,…) in any hole depends on the scientific objectives and operational constraints.
IODP Expedition 397, Hole U1586D - Well Logging Data
Logging data are measurements of physical properties of the formation surrounding a borehole, acquired in situ after completion of coring (wireline logging) or during drilling (Logging-While-Drilling, LWD). The range of data (resistivity, gamma radiation, velocity, density, borehole images,…) in any hole depends on the scientific objectives and operational constraints.
Investigating the resilience of termite communities to logging and climate change in Borneo
<b>Description: </b><p>This project set out to quantify the tolerance of termite communities to climate change, or more specifically, temperature and humidity change, two climatic variables that have been hypothesised to drive species distributions (particularly for small ectotherms such as termites). The data presented here are the tolerances of termites to increasing temperatures, and decreasing humidities. <br><br>The thermal data was recorded by inserting termites into individual glass vials, placing those sealed vials into a water bath, and increasing the temperature until they could no longer function. This temperature was recorded, and taken as CTmax (Critical Thermal Maximum), for each individual termite. These data can be found in the TemperatureData worksheet. <br><br>The humidity data was recorded slightly differently. Groups of termites (of the same genus) were weighed and placed in one of two types of glass vial. Dessicated vials also contained silica gel (and a barrier to prevent termite interaction with the gel) which reduced the humidity to an average of 30%. Control vials did not contain any silica gel and had an average humidity of 85%. These vials were removed at one of 5 time points, and the termites were weighed again, and weight change was recorded. This weight change was attributed to water loss. <br><br>The body water data was used to calculate the proportion of body mass that was water, for multiple termite genera. This was done so that percentage of body water lost could be calculated for the humidity experiment, rather than an absolute value of water loss (as termites vary in size, using absolute values would cause false conclusions). </p><p><b>Project: </b>This dataset was collected as part of the following SAFE research project: <a href="https://www.safeproject.net/projects/project_view/31"><b>Investigating the resilience of termite communities to logging and climate change in Borneo</b></a></p><p><b>XML metadata: </b>GEMINI compliant metadata for this dataset is available <a href="https://www.safeproject.net/datasets/xml_metadata?id=33">here</a></p><p><b>Data worksheets: </b>There are 3 data worksheets in this dataset:</p><ol><li><p><b>Thermal tolerance data</b> (Worksheet TemperatureData)</p><p>Dimensions: 1256 rows by 17 columns</p><p>Description: Thermal tolerance data of termites</p><p>Fields: </p><ul><li><b>Nest_no</b>: The unique nest (colony) number that each termite was taken from (Field type: ID)</li><li><b>Day</b>: The day on which the experiment took place (Field type: ID)</li><li><b>Termite_no</b>: The unique termite number, missing numbers are due to non-experimental deaths (Field type: ID)</li><li><b>Experiment</b>: Whether it was the first or second experiment from the same colony (Field type: Replicate)</li><li><b>Family</b>: The family of the termite (Field type: ID)</li><li><b>Genus</b>: The genus of the termite (Field type: ID)</li><li><b>Species</b>: The species (where known) of the termite (Field type: ID)</li><li><b>Name</b>: The species (where known) of the termite (Field type: Taxa)</li><li><b>CTmax</b>: The critical thermal maximum of the termite, or the temperature that it died at (Field type: Numeric Trait)</li><li><b>Sampling_zone</b>: Sampling area, LFE corresponds to the area at the SAFE project, and OP is Oil Palm (Field type: Categorical)</li><li><b>Forest_type</b>: Forest type sampled from within the sampling area, OG corresponds to Old Growth (or pristine) forest (Field type: Categorical)</li><li><b>Nest_type</b>: The type of nest that the termite builds (Field type: Categorical Trait)</li><li><b>Nest_Layer</b>: The layer within the forest that the nest is built (Field type: Categorical Trait)</li><li><b>Food_group</b>: The food group that the termite belongs to, categorised using the latest literature (Field type: Categorical Trait)</li><li><b>Body</b>: The level of sclerotisation of the termite (Field type: Categorical Trait)</li><li><b>Caste</b>: Which behavioural caste the termite belonged to (Field type: Categorical Trait)</li></ul><br></li><li><p><b>Humidity tolerance data</b> (Worksheet HumidityData)</p><p>Dimensions: 169 rows by 16 columns</p><p>Description: Humidity tolerance data of 4 termite genera</p><p>Fields: </p><ul><li><b>Nest_no</b>: The unique nest (colony) number that the termites were taken from (Field type: ID)</li><li><b>Tube</b>: The unique tube number that the termites were placed in (Field type: ID)</li><li><b>Taxa</b>: The species (where known) of the termite (Field type: Taxa)</li><li><b>Time</b>: The five time points that the tubes were removed at (Field type: Numeric)</li><li><b>Treatment</b>: Whether the termites were placed in a control or desiccated tube (Field type: Categorical)</li><li><b>Initial</b>: Weight of the group of termites at the start of the experiment (Field type: Numeric Trait)</li><li><b>Finish</b>: Weight of group of termites when removed from experiment (Field type: Numeric Trait)</li><li><b>Percentage_lost</b>: Proportion of body mass change (Field type: Numeric Trait)</li><li><b>Sampling_zone</b>: Sampling area, LFE corresponds to the area at the SAFE project, and OP is Oil Palm (Field type: Categorical)</li><li><b>Forest_type</b>: Forest type sampled from within the sampling area, OG corresponds to Old Growth (or pristine) forest (Field type: Categorical)</li><li><b>Food_group</b>: The food group that the termite belongs to, categorised using the latest literature (Field type: Categorical Trait)</li><li><b>Body</b>: The level of sclerotisation of the termite (Field type: Categorical Trait)</li><li><b>No_termites</b>: Number of termites placed in the tube (Field type: Numeric)</li><li><b>No_dead</b>: Number of termites that were dead at the point of the second weighing (Field type: Numeric)</li><li><b>Percentage_Dead</b>: Percentage of termites that are dead at point of second weighing (Field type: Numeric)</li></ul><br></li><li><p><b>Termite total body water data</b> (Worksheet BodyWaterData)</p><p>Dimensions: 38 rows by 12 columns</p><p>Description: Data calculating the total body water of 4 termite genera, this data was used in the humidity data to calculate the percentage of body water lost during the experiment</p><p>Fields: </p><ul><li><b>Nest_no</b>: The unique nest (colony) number that the termites were taken from (Field type: ID)</li><li><b>Tray_no</b>: The unique tray number that the termites were placed in (Field type: ID)</li><li><b>Genus</b>: The species (where known) of the termite (Field type: Taxa)</li><li><b>Weight_start</b>: Weight of the group of termites at the start of the experiment (Field type: Numeric Trait)</li><li><b>Weight_end</b>: Weight of group of termites when removed from experiment (Field type: Numeric Trait)</li><li><b>Percentage</b>: Percentage of body mass that is water (Field type: Numeric Trait)</li><li><b>Sampling_zone</b>: Sampling area, LFE corresponds to the area at the SAFE project, and OP is Oil Palm (Field type: Categorical)</li><li><b>Forest_type</b>: Forest type sampled from within the sampling area, OG corresponds to Old Growth (or pristine) forest (Field type: Categorical)</li><li><b>Food_group</b>: The food group that the termite belongs to, categorised using the latest literature (Field type: Categorical Trait)</li><li><b>Body</b>: The level of sclerotisation of the termite (Field type: Categorical Trait)</li><li><b>Caste</b>: Which behavioural caste the termite belonged to (Field type: Categorical Trait)</li></ul><br></li></ol><p><b>Date range: </b>2016-02-01 to 2016-07-01</p><p><b>Latitudinal extent: </b>4.5000 to 5.0700</p><p><b>Longitudinal extent: </b>116.7500 to 117.8200</p><p><b>Taxonomic coverage: </b><br> All taxon names are validated against the GBIF backbone taxonomy. If a dataset uses a synonym, the accepted usage is shown followed by the dataset usage in brackets. Taxa that cannot be validated, including new species and other unknown taxa, morphospecies, functional groups and taxonomic levels not used in the GBIF backbone are shown in square brackets.</p><div>Animalia<br> - Arthropoda<br> -  - Insecta<br> -  -  - Isoptera<br> -  -  -  -  - <i>Homallotermes</i><br> -  -  -  -  -  - [<i>Homallotermes foraminifer</i>]<br> -  -  -  - Kalotermitidae<br> -  -  -  -  - <i>Glyptotermes</i><br> -  -  -  -  -  - [Glyptotermes sp.]<br> -  -  -  - Rhinotermitidae<br> -  -  -  -  - <i>Coptotermes</i><br> -  -  -  -  -  - [Coptotermes sp.]<br> -  -  -  -  - <i>Parrhinotermes</i><br> -  -  -  -  -  - [<i>Parrhinotermes pygmaeus</i>]<br> -  -  -  -  - <i>Schedorhinotermes</i><br> -  -  -  -  -  - [<i>Schedorhinotermes sarawakensis</i>]<br> -  -  -  -  -  - [Schedorhinotermes sp.]<br> -  -  -  - Termitidae<br> -  -  -  -  - <i>Bulbitermes</i><br> -  -  -  -  -  - [Bulbitermes sp.]<br> -  -  -  -  - <i>Dicuspiditermes</i><br> -  -  -  -  -  - [Dicuspiditermes sp.]<br> -  -  -  -  - <i>Globitermes</i><br> -  -  -  -  -  - [<i>Globitermes globosus</i>]<br> -  -  -  -  - <i>Hospitalitermes</i><br> -  -  -  -  -  - [<i>Hospitalitermes hospitalis</i>]<br> -  -  -  -  -  - [<i>Hospitalitermes bicolour</i>]<br> -  -  -  -  - [Lacessitermes sp.]<br> -  -  -  -  - <i>Longipeditermes</i><br> -  -  -  -  -  - [Longipeditermes sp.]<br> -  -  -  -  - <i>Macrotermes</i><br> -  -  -  -  -  - [<i>Macrotermes gilvus</i>]<br> -  -  -  -  - <i>Microcerotermes</i><br> -  -  -  -  -  - [Microcerotermes sp.]<br> -  -  -  -  - <i>Nasutitermes</i><br> -  -  -  -  -  - [<i>Nasutitermes havilandi</i>]<br> -  -  -  -  -  - [Nasutitermes sp.]<br> -  -  -  -  - <i>Odontotermes</i><br> -  -  -  -  -  - [Odontotermes sp.]<br></div><p></p>
Investigating small mammal microhabitat selection in logged and unlogged tropical forests
<b>Description: </b><p>Spool and line tracking data on small mammals</p><p><b>Project: </b>This dataset was collected as part of the following SAFE research project: <a href="https://www.safeproject.net/projects/project_view/87"><b>Investigating small mammal microhabitat selection in logged and unlogged tropical forests</b></a></p><p><b>XML metadata: </b>GEMINI compliant metadata for this dataset is available <a href="https://www.safeproject.net/datasets/xml_metadata?id=60">here</a></p><p><b>Data worksheets: </b>There are 3 data worksheets in this dataset:</p><ol><li><p><b>Tracking data</b> (Worksheet Tracking)</p><p>Dimensions: 1396 rows by 15 columns</p><p>Description: Individual trap segment details for all spool-and-line tracked individuals</p><p>Fields: </p><ul><li><b>block</b>: SAFE Project Block in which trapping grid was located (Field type: Location)</li><li><b>Date</b>: Date individual was spooled (Field type: Date)</li><li><b>Species</b>: Species identity (Field type: Taxa)</li><li><b>Trap</b>: Trap number on the grid where individual was captured (Field type: ID)</li><li><b>Respool</b>: Has this individual been tracked previously? (Field type: Categorical)</li><li><b>track</b>: Track ID for that day (Field type: Replicate)</li><li><b>Pit.tag.no.</b>: PIT tag number of the individual being tracked (Field type: ID)</li><li><b>Sex</b>: Sex oFxthe individual (Field type: Categorical)</li><li><b>Weight</b>: Body mass of the individual (Field type: Numeric)</li><li><b>Distance</b>: Length of straight line portion of track (Field type: Numeric)</li><li><b>Bearing</b>: Compass bearing of track portion (Field type: Numeric)</li><li><b>Dominant.habitat.feature</b>: Habitat taype on the observed route (Field type: Categorical)</li><li><b>feature.control</b>: Habitat type on the control route (Field type: Categorical)</li><li><b>height</b>: Height above ground (Field type: Ordered Categorical)</li></ul><br></li><li><p><b>microhabitat data</b> (Worksheet microhabitat)</p><p>Dimensions: 597 rows by 15 columns</p><p>Description: Microhabitat details recorded along spool tracks</p><p>Fields: </p><ul><li><b>Species</b>: Species identity (Field type: Taxa)</li><li><b>individual</b>: PIT tag number of the individual being tracked (Field type: ID)</li><li><b>Control</b>: Is the record for the observed track of the control track? (Field type: Categorical)</li><li><b>ground</b>: Leaf density <0.5m above ground (Field type: Ordered Categorical)</li><li><b>understorey</b>: Leaf density 0.5m to 3m above ground (Field type: Ordered Categorical)</li><li><b>midstorey</b>: Leaf density 3m to 20m above ground (Field type: Ordered Categorical)</li><li><b>canopy</b>: Leaf density >20m above ground (Field type: Ordered Categorical)</li><li><b>forest.quality</b>: Forest quality (Field type: Ordered Categorical)</li><li><b>Predator</b>: Predation risk (Field type: Ordered Categorical)</li><li><b>Densiometer</b>: Canopy cover (Field type: Numeric)</li><li><b>Relascope</b>: Tree volume (Field type: Numeric)</li><li><b>height</b>: Height above ground (Field type: Ordered Categorical)</li><li><b>rain</b>: Rainfall (Field type: Ordered Categorical)</li><li><b>moon.phase</b>: Lunar phase (Field type: Ordered Categorical)</li></ul><br></li><li><p><b>environmental data</b> (Worksheet trap_covariates)</p><p>Dimensions: 295 rows by 14 columns</p><p>Description: Environmental quality metrics at trap locations</p><p>Fields: </p><ul><li><b>Site</b>: Site locality in camera trap grid (Field type: Location)</li><li><b>trap</b>: Trap identity within block (Field type: ID)</li><li><b>ground</b>: Leaf density <0.5m above ground (Field type: Ordered Categorical)</li><li><b>understorey</b>: Leaf density 0.5m to 3m above ground (Field type: Ordered Categorical)</li><li><b>midstorey</b>: Leaf density 3m to 20m above ground (Field type: Ordered Categorical)</li><li><b>canopy</b>: Leaf density >20m above ground (Field type: Ordered Categorical)</li><li><b>forest quality (O)</b>: Forest quality (Field type: Ordered Categorical)</li><li><b>Predator</b>: Predation risk (Field type: Ordered Categorical)</li><li><b>Densiometer 1</b>: Canopy cover - 1 of 4 measurements (Field type: Numeric)</li><li><b>Densiometer 2</b>: Canopy cover - 1 of 4 measurements (Field type: Numeric)</li><li><b>Densiometer 3</b>: Canopy cover - 1 of 4 measurements (Field type: Numeric)</li><li><b>Densiometer 4</b>: Canopy cover - 1 of 4 measurements (Field type: Numeric)</li><li><b>Relascope</b>: Tree volume (Field type: Numeric)</li></ul><br></li></ol><p><b>Date range: </b>2012-06-01 to 2012-07-21</p><p><b>Latitudinal extent: </b>4.6931 to 4.7166</p><p><b>Longitudinal extent: </b>117.5304 to 117.5975</p><p><b>Taxonomic coverage: </b><br> All taxon names are validated against the GBIF backbone taxonomy. If a dataset uses a synonym, the accepted usage is shown followed by the dataset usage in brackets. Taxa that cannot be validated, including new species and other unknown taxa, morphospecies, functional groups and taxonomic levels not used in the GBIF backbone are shown in square brackets.</p><div>Animalia<br> - Chordata<br> -  - Mammalia<br> -  -  - Rodentia<br> -  -  -  - Muridae<br> -  -  -  -  - <i>Chrotomys</i><br> -  -  -  -  -  - <i>Chrotomys whiteheadi</i> (as <i>Maxomys whiteheadi</i>)<br> -  -  -  -  - <i>Leopoldamys</i><br> -  -  -  -  -  - <i>Leopoldamys sabanus</i><br> -  -  -  -  - <i>Maxomys</i><br> -  -  -  -  -  - <i>Maxomys surifer</i><br> -  -  -  -  - <i>Rattus</i><br> -  -  -  -  -  - <i>Rattus rattus</i><br></div><p></p>
Deadwood carbon stocks under logging and fragmentation impacts
<b>Description: </b><p>Wood density estimates of deadwood across decomposition classes</p><p><b>Project: </b>This dataset was collected as part of the following SAFE research project: <a href="https://www.safeproject.net/projects/project_view/23"><b>Deadwood carbon stocks under logging and fragmentation impacts</b></a></p><p><b>XML metadata: </b>GEMINI compliant metadata for this dataset is available <a href="https://www.safeproject.net/datasets/xml_metadata?id=79">here</a></p><p><b>Data worksheets: </b>There are 1 data worksheets in this dataset:</p><ol><li><p><b>Wood density estimates</b> (Worksheet WoodDensity)</p><p>Dimensions: 418 rows by 23 columns</p><p>Description: Estimates of wood density for deadwood samples</p><p>Fields: </p><ul><li><b>Site</b>: Specific locations where deadwood samples were collected (Field type: Location)</li><li><b>Location</b>: SAFE Project sample block where deadwood samples were collected from (Field type: Location)</li><li><b>Block</b>: SAFE Project sample block where deadwood samples were collected from (Field type: ID)</li><li><b>Samples</b>: Unique identifier for each deadwood item sampled from in the field (Field type: Replicate)</li><li><b>DecayClass</b>: Decomposition level of the deadwood sample (Field type: Ordered Categorical)</li><li><b>SubS</b>: Replicate number. Multiple samples were analysed from a single 'Samples' (Field type: Replicate)</li><li><b>DeadPiece</b>: Type of the deadwood item in the field that the sample for analysis was extracted from (Field type: Categorical)</li><li><b>SpeciesID</b>: Identity of the deadwood item in the field that the sample for analysis was extracted from (Field type: Taxa)</li><li><b>D_upper_cm</b>: Diameter at one end of the deadwood item in the field that the sample for analysis was extracted from (Field type: Numeric)</li><li><b>D_lower_cm</b>: Diameter at other end of the deadwood item in the field that the sample for analysis was extracted from (Field type: Numeric)</li><li><b>Length_cm</b>: Length of the deadwood item in the field that the sample for analysis was extracted from (Field type: Numeric)</li><li><b>Type</b>: Shape of the deadwood sample being analysed (Field type: Categorical)</li><li><b>MassFresh _ g</b>: Wet weight of the deadwood sample (Field type: Numeric)</li><li><b>L1_mm</b>: Dimension measurement (Field type: Numeric)</li><li><b>L2_mm</b>: Dimension measurement (Field type: Numeric)</li><li><b>L3_mm</b>: Dimension measurement (Field type: Numeric)</li><li><b>V_fresh_ml</b>: Volume of the deadwood sample (Field type: Numeric)</li><li><b>MassDry_g</b>: Dry weight of the deadwood sample (Field type: Numeric)</li><li><b>V_dry_ml</b>: Volume of the deadwood sample (Field type: Numeric)</li><li><b>V_Piece_cm3</b>: Volume of the deadwood sample (Field type: Numeric)</li><li><b>V_Piece_cm3_set5</b>: Volume of the deadwood sample (Field type: Numeric)</li><li><b>Density</b>: Wood density (Field type: Numeric)</li></ul><br></li></ol><p><b>Date range: </b>2012-01-01 to 2013-12-31</p><p><b>Latitudinal extent: </b>4.6880 to 4.7436</p><p><b>Longitudinal extent: </b>117.5346 to 117.6290</p><p><b>Taxonomic coverage: </b><br> All taxon names are validated against the GBIF backbone taxonomy. If a dataset uses a synonym, the accepted usage is shown followed by the dataset usage in brackets. Taxa that cannot be validated, including new species and other unknown taxa, morphospecies, functional groups and taxonomic levels not used in the GBIF backbone are shown in square brackets.</p><div>Plantae<br> - [Kayu malam]<br> - [Laran]<br> - [Sadaman egari]<br> - [Sedaman]<br> - Tracheophyta<br> -  - Magnoliopsida<br> -  -  - Malpighiales<br> -  -  -  - Euphorbiaceae<br> -  -  -  -  - <i>Macaranga</i><br></div><p></p>
Interaction event data logged by the SMASH medication safety dashboard
<p>Interaction event data logged by the SMASH medication safety dashboard from 21 January 2016 to 13 October 2016.</p>
Do logging roads impede small mammal movement in Borneo's tropical rainforests?
<b>Description: </b><p>Data from small mammal trap grid adjacent to roads and an associated movement/translocation experiment</p><p><b>Project: </b>This dataset was collected as part of the following SAFE research project: <a href="https://www.safeproject.net/projects/project_view/37"><b>Do logging roads impede small mammal movement in Borneo's tropical rainforests?</b></a></p><p><b>XML metadata: </b>GEMINI compliant metadata for this dataset is available <a href="https://www.safeproject.net/datasets/xml_metadata?id=113">here</a></p><p><b>Files: </b>This consists of 1 file: template_Heon.xlsx</p><p><b>template_Heon.xlsx</b></p><p>This file contains dataset metadata and 1 data tables:</p><ol><li><p><b>Road crossing field data</b> (described in worksheet RoadCrossing)</p><p>Description: Data from trap grid plus translocation experiment; NB: Paper accompanying this dataset used data from Site1-7 only; no translocations were conducted at Site8 so this was not used in the paper.</p><p>Number of fields: 23</p><p>Number of data rows: 3456</p><p>Fields: </p><ul><li><b>Site</b>: Site code (sites not georeferenced) (Field type: Location)</li><li><b>Treatment</b>: Experimental treatment trap was assigned to (Field type: Categorical)</li><li><b>Road.width</b>: Width of the road adjacent to trap grid (Field type: Numeric)</li><li><b>Date</b>: Date trap was set (Field type: Date)</li><li><b>Trap.Night</b>: Number of nights trap had been set at this site for (Field type: Numeric)</li><li><b>Trap.Number</b>: For field reference on distance and location of each trap. (Field type: ID)</li><li><b>Set.distance</b>: Distance from the road's edge or the start point in control sites. (Field type: Numeric)</li><li><b>Rat.Present</b>: Trap status (Field type: Categorical)</li><li><b>Distance.fromroad</b>: distance of the trap site from a road (Field type: Numeric)</li><li><b>Trap.Status</b>: Basic information about captured individuals (Field type: Categorical)</li><li><b>Species</b>: Species identity (Field type: Taxa)</li><li><b>Weight</b>: Body mass (Field type: Numeric)</li><li><b>Hind.foot</b>: Length of hind foot (Field type: Numeric)</li><li><b>Ear</b>: Length of ear (Field type: Numeric)</li><li><b>AGD</b>: Anal-genital distance (Field type: Numeric)</li><li><b>Sex</b>: Sex of the individual (Field type: Categorical)</li><li><b>Age</b>: Age of the individual (Field type: Categorical)</li><li><b>Release.distance</b>: Distance on the trap grid that the rat was released from (Field type: Numeric)</li><li><b>Returned.translocation</b>: Was the rat recaptured after translocation? (Field type: Categorical)</li><li><b>Recaptured.trap</b>: Trap ID code (Field type: ID)</li><li><b>Recaptured.Date</b>: Date rat was recaptured on trap grid after translocation (Field type: Date)</li><li><b>Recaptured.Distance</b>: Distance on the trap grid where the rat was re-captured (returned) from translocation (Field type: Numeric)</li><li><b>Recaptured.Day</b>: Day the rat is re-captured /return from translocation to trap grid (Field type: Numeric)</li></ul></li></ol><p><b>Date range: </b>2016-04-19 to 2016-07-20</p><p><b>Latitudinal extent: </b>4.6893 to 4.7472</p><p><b>Longitudinal extent: </b>117.5817 to 117.6158</p><p><b>Taxonomic coverage: </b><br> All taxon names are validated against the GBIF backbone taxonomy. If a dataset uses a synonym, the accepted usage is shown followed by the dataset usage in brackets. Taxa that cannot be validated, including new species and other unknown taxa, morphospecies, functional groups and taxonomic levels not used in the GBIF backbone are shown in square brackets.</p><div>Animalia<br> - Chordata<br> -  - Mammalia<br> -  -  - Rodentia<br> -  -  -  - Muridae<br> -  -  -  -  - <i>Chrotomys</i><br> -  -  -  -  -  - <i>Chrotomys whiteheadi</i><br> -  -  -  -  - <i>Leopoldamys</i><br> -  -  -  -  -  - <i>Leopoldamys sabanus</i><br> -  -  -  -  - <i>Maxomys</i><br> -  -  -  -  -  - <i>Maxomys baeodon</i><br> -  -  -  -  -  - <i>Maxomys rajah</i><br> -  -  -  -  -  - <i>Maxomys surifer</i><br> -  -  -  -  - <i>Niviventer</i><br> -  -  -  -  -  - <i>Niviventer cremoriventer</i><br> -  -  -  -  - <i>Rattus</i><br> -  -  -  -  -  - <i>Rattus exulans</i><br> -  -  -  -  - <i>Sundamys</i><br> -  -  -  -  -  - <i>Sundamys muelleri</i><br></div><p></p>
GRB 070306: Observing log and results from photometry
<p>Observation log and photometric results of GRB 070306 from Jaunsen et al. (2008), Ap.J. 681, p.453-461</p> <p> </p>
The output and the log files from RNA-Seq workflow benchmark for CWL-metrics manuscript
<p>The output files and log files generated by the workflow executions for RNA-Seq workflow benchmark by CWL-metrics, from the manuscript "Accumulating computational resource usage of genomic data analysis workflow to optimize cloud computing instance selection" (https://doi.org/10.1101/456756).</p>
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.