The data (name, year of birth, sex, and number) are from a 100 percent sample of Social Security card applications for 1880 onward.

This data set lists the sex and number of birth registrations for each first name, from 1900 onward. Years are grouped by the date of the birth registration, not by the date of birth. Some birth registrations are not included, such as registrations with a sex other than Male or Female (i.e. indeterminate or not recorded), or where the birth registration date is not recorded. These excluded records are so few their exclusion is unlikely to have any significant impact on the data. Where a name has less than 10 instances in a particular year, the name will not be included in the data for that year. Due to this, total volumes will be less than the total birth registrations in that year. As first and middle names are recorded in our system together, the first name has been split off from the middle names. Due to the size of the data set, this was done with an automated system, generally looking for the first space in the name. This means there may be names not correctly added. Also, certain symbols in names may not carry through to the data correctly. Please let us know using the contact email address if you find any errors in the data.

Popular Baby Names by Sex and Ethnic Group Data were collected through civil birth registration. Each record represents the ranking of a baby name in the order of frequency. Data can be used to represent the popularity of a name. Caution should be used when assessing the rank of a baby name if the frequency count is close to 10; the ranking may vary year to year.

This dataset contains statistics on names (first names of women, first names of men, and last names) by country of birth. In total, there are 231,505 names by 202 countries. The data comes from Statistics Sweden's population statistics (name register) and refers to persons registered in Sweden on December 31st, 2020. However, some names are excluded due to confidentiality, such as names with fewer than five carriers. The data is licensed with Creative Commons Attribution 4.0 International (CC BY 4.0) and may be used as long as Statistics Sweden is stated as the source. In this dataset, you will also find (in addition to the original data from Statistics Sweden) tidied data where the ISO code for each country has been added, as well as data in so-called wide format and long format to facilitate easier data processing.

Please see the Swedish version of the post and the README file for more information about the data.

List of male and female baby names in South Australia from 1944 to 2024. The annual data for baby names is published January/February each year.

Company Datasets for valuable business insights!

Discover new business prospects, identify investment opportunities, track competitor performance, and streamline your sales efforts with comprehensive Company Datasets.

These datasets are sourced from top industry providers, ensuring you have access to high-quality information:

• Owler: Gain valuable business insights and competitive intelligence. -AngelList: Receive fresh startup data transformed into actionable insights. -CrunchBase: Access clean, parsed, and ready-to-use business data from private and public companies. -Craft.co: Make data-informed business decisions with Craft.co's company datasets. -Product Hunt: Harness the Product Hunt dataset, a leader in curating the best new products.

We provide fresh and ready-to-use company data, eliminating the need for complex scraping and parsing. Our data includes crucial details such as:

• Company name;
• Size;
• Founding date;
• Location;
• Industry;
• Revenue;
• Employee count;
• Competitors.

You can choose your preferred data delivery method, including various storage options, delivery frequency, and input/output formats.

Receive datasets in CSV, JSON, and other formats, with storage options like AWS S3 and Google Cloud Storage. Opt for one-time, monthly, quarterly, or bi-annual data delivery.

With Oxylabs Datasets, you can count on:

• Fresh and accurate data collected and parsed by our expert web scraping team.
• Time and resource savings, allowing you to focus on data analysis and achieving your business goals.
• A customized approach tailored to your specific business needs.
• Legal compliance in line with GDPR and CCPA standards, thanks to our membership in the Ethical Web Data Collection Initiative.

Pricing Options:

Standard Datasets: choose from various ready-to-use datasets with standardized data schemas, priced from $1,000/month.

Custom Datasets: Tailor datasets from any public web domain to your unique business needs. Contact our sales team for custom pricing.

Experience a seamless journey with Oxylabs:

• Understanding your data needs: We work closely to understand your business nature and daily operations, defining your unique data requirements.
• Developing a customized solution: Our experts create a custom framework to extract public data using our in-house web scraping infrastructure.
• Delivering data sample: We provide a sample for your feedback on data quality and the entire delivery process.
• Continuous data delivery: We continuously collect public data and deliver custom datasets per the agreed frequency.

Unlock the power of data with Oxylabs' Company Datasets and supercharge your business insights today!

All cities with a population > 1000 or seats of adm div (ca 80.000)Sources and ContributionsSources : GeoNames is aggregating over hundred different data sources. Ambassadors : GeoNames Ambassadors help in many countries. Wiki : A wiki allows to view the data and quickly fix error and add missing places. Donations and Sponsoring : Costs for running GeoNames are covered by donations and sponsoring.Enrichment:add country name

Context

RxNorm is a name of a US-specific terminology in medicine that contains all medications available on US market. Source: https://en.wikipedia.org/wiki/RxNorm

RxNorm provides normalized names for clinical drugs and links its names to many of the drug vocabularies commonly used in pharmacy management and drug interaction software, including those of First Databank, Micromedex, Gold Standard Drug Database, and Multum. By providing links between these vocabularies, RxNorm can mediate messages between systems not using the same software and vocabulary. Source: https://www.nlm.nih.gov/research/umls/rxnorm/

Content

RxNorm was created by the U.S. National Library of Medicine (NLM) to provide a normalized naming system for clinical drugs, defined as the combination of {ingredient + strength + dose form}. In addition to the naming system, the RxNorm dataset also provides structured information such as brand names, ingredients, drug classes, and so on, for each clinical drug. Typical uses of RxNorm include navigating between names and codes among different drug vocabularies and using information in RxNorm to assist with health information exchange/medication reconciliation, e-prescribing, drug analytics, formulary development, and other functions.

This public dataset includes multiple data files originally released in RxNorm Rich Release Format (RXNRRF) that are loaded into Bigquery tables. The data is updated and archived on a monthly basis.

The following tables are included in the RxNorm dataset:

• RXNCONSO contains concept and source information

• RXNREL contains information regarding relationships between entities

• RXNSAT contains attribute information

• RXNSTY contains semantic information

• RXNSAB contains source info

• RXNCUI contains retired rxcui codes

• RXNATOMARCHIVE contains archived data

• RXNCUICHANGES contains concept changes

Update Frequency: Monthly

Fork this kernel to get started with this dataset.

Acknowledgements

https://www.nlm.nih.gov/research/umls/rxnorm/

https://bigquery.cloud.google.com/dataset/bigquery-public-data:nlm_rxnorm

https://cloud.google.com/bigquery/public-data/rxnorm

Dataset Source: Unified Medical Language System RxNorm. The dataset is provided "AS IS" without any warranty, express or implied, from Google. Google disclaims all liability for any damages, direct or indirect, resulting from the use of the dataset. This dataset uses publicly available data from the U.S. National Library of Medicine (NLM), National Institutes of Health, Department of Health and Human Services; NLM is not responsible for the dataset, does not endorse or recommend this or any other dataset.

Banner Photo by @freestocks from Unsplash.

Inspiration

What are the RXCUI codes for the ingredients of a list of drugs?

Which ingredients have the most variety of dose forms?

In what dose forms is the drug phenylephrine found?

What are the ingredients of the drug labeled with the generic code number 072718?

Dataset 1

Presentation

 This dataset was collected between 2012 and 2013 in Rennes (France) during two conditions (visual naming and spelling tasks).
 The dataset consists of naming and spelling the names of visually presented objects. The data was collected in the Rennes University Hospital. This experiment was approved by an independent ethics committee and authorized by the French institutional review board (IRB): "Comite de Protection des Personnes dans la Recherche Biomedicale Ouest V" (CCPPRB-Ouest V).
 This study was registered under the name "conneXion" and the agreement number: 2012- A01227-36.

Participants

 Twenty-three right-handed healthy volunteers of whom 12 females, with an age range between
 19 and 40 years (mean age 28 year),and 11 males with an age range between 19 and 33 years (mean age 23 years) participated in this study. (See participants.json and participants.tsv for more details)

Experiment

 * The experiment begins with the verification of inclusion/exclusion criteria.
 * The participants read the information notice and the consent form. 
 * Then they sign two questionnaires. 
 * One subject -->Two conditions (naming and spelling)--> two runs for each condition.
 * Each run contains 74 stimuli.
 * The spelling task always follow the naming task and its instruction was not given before the naming task was completed to avoid any reminiscence of words orthographic structures
 * Each run contains balanced numbers of animals and objects as well as long and short words.
 * Pictures are presented on a screen using a computer and the experimental paradigm is presented using E-prime Psychology Software Tools. 
 * The responses produced by the participants were collected via a Logitech microphone and analyzed to detect onsets of speech using Praat v5.3.13(University of Amsterdam, 1012VT Amsterdam, The Netherlands).

EEG acquisition

 * HD-EEG system (EGI, Electrical Geodesic Inc., 256 electrodes) 
 * Sampling frequency: 1000Hz
 * Impedances were kept below 5k

Contact

 * If you have any questions or comments, please contact: 
 * Ahmad Mheich: mheich.ahmad@gmail.com

This release presents experimental statistics from the Mental Health Services Data Set (MHSDS), using final submissions for April 2016 and provisional submissions for May 2016. This is the fifth monthly release from the dataset, which replaces the Mental Health and Learning Disabilities Dataset (MHLDDS). As well as analysis of waiting times, first published in March 2016, this release includes elements of the reports that were previously included in monthly reports produced from final MHLDDS submissions. In this publication a new data file has been produced to present the data for people identified as having learning disabilities and/or autistic spectrum disorder (LDA) characteristics. Because of the scope of the changes to the dataset (resulting in the name change to MHSDS and the new name for these monthly reports) it will take time to re-introduce all possible measures that were previously part of the MHLDS Monthly Reports. Additional measures will be added to this report in the coming months. Further details about these changes and the consultation that informed were announced in November. From January 2016 the release includes information on people in children and young people's mental health services, including CAMHS, for the first time. Learning disabilities and autism services have been included since September 2014. This release of final data for April 2016 comprises: - An Executive Summary, which presents national-level analysis across the whole dataset and also for some specific service areas and age groups - Data tables about access and waiting times in mental health services for the based on provisional data for the period 1 March 2016 to 31 May 2016. - A monthly data file which presents 92 measures for mental health, learning disability and autism services at National, Provider and Clinical Commissioning Group (CCG) level. - A Currency and Payments (CAP) data file, containing three measures relating to people assigned to Adult Mental Health Care Clusters. Further measures will be added in future releases. - A data file containing the measures relating to people with learning disabilities and/or autism. - Exploratory analysis of the coverage and completeness of access and waiting times statistics for people entering the Early Intervention in Psychosis pathway. - A set of provider level data quality measures for both months. The report comprises of validity measures for various data items at National and Provider level. From the publication of April data, a coverage report is included showing the number of providers submitting each month and number of records submitted. - A metadata file, which provide contextual information for each measure, including a full description, current uses, method used for analysis and some notes on usage. We will release the reports as experimental statistics until the characteristics of data flowed using the new data standard are understood. A correction has been made to this publication on 10 September 2018. This amendment relates to statistics in the monthly CSV data file; the specific measures effected are listed in the “Corrected Measures” CSV. All listed measures have now been corrected. NHS Digital apologises for any inconvenience caused.

Context

The New York Times is releasing a series of data files with cumulative counts of coronavirus cases in the United States, at the state and county level, over time. They are compiling this time series data from state and local governments and health departments in an attempt to provide a complete record of the ongoing outbreak.

Content

As described on the NYTimes Github page.

For each date, we show the cumulative number of confirmed cases and deaths as reported that day in that county or state. All cases and deaths are counted on the date they are first announced.

In some instances, we report data from multiple counties or other non-county geographies as a single county. For instance, we report a single value for New York City, comprising the cases for New York, Kings, Queens, Bronx and Richmond Counties. In these instances the FIPS code field will be empty. (We may assign FIPS codes to these geographies in the future.) See the list of geographic exceptions.

Cities like St. Louis and Baltimore that are administered separately from an adjacent county of the same name are counted separately.

“Unknown” Counties Many state health departments choose to report cases separately when the patient’s county of residence is unknown or pending determination. In these instances, we record the county name as “Unknown.” As more information about these cases becomes available, the cumulative number of cases in “Unknown” counties may fluctuate.

Sometimes, cases are first reported in one county and then moved to another county. As a result, the cumulative number of cases may change for a given county.

Geographic Exceptions New York City All cases for the five boroughs of New York City (New York, Kings, Queens, Bronx and Richmond counties) are assigned to a single area called New York City.

Kansas City, Mo. Four counties (Cass, Clay, Jackson and Platte) overlap the municipality of Kansas City, Mo. The cases and deaths that we show for these four counties are only for the portions exclusive of Kansas City. Cases and deaths for Kansas City are reported as their own line.

Joplin, Mo. Joplin is reported separately from Jasper and Newton Counties.

Chicago All cases and deaths for Chicago are reported as part of Cook County.

Acknowledgements

Thanks to the New York Times for providing this data. https://www.nytimes.com/interactive/2020/us/coronavirus-us-cases.html

The Gitbub repository can be found here: https://github.com/nytimes/covid-19-data

Open-access database of englacial temperature measurements compiled from data submissions and published literature. It is developed on GitHub and published to Zenodo.

Data structure

The dataset adheres to the Frictionless Data Tabular Data Package specification. The metadata in datapackage.json describes, in detail, the contents of the tabular data files in the data folder:

source.csv: Description of each data source (either a personal communication or the reference to a published study).

borehole.csv: Description of each borehole (location, elevation, etc), linked to source.csv via source_id and less formally via source identifiers in notes.

profile.csv: Description of each profile (date, etc), linked to borehole.csv via borehole_id and to source.csv via source_id and less formally via source identifiers in notes.

measurement.csv: Description of each measurement (depth and temperature), linked to profile.csv via borehole_id and profile_id.

For boreholes with many profiles (e.g. from automated loggers), pairs of profile.csv and measurement.csv are stored separately in subfolders of data named {source.id}-{glacier}, where glacier is a simplified and kebab-cased version of the glacier name (e.g. flowers2022-little-kluane).

data/source.csv

Sources of information considered in the compilation of this database. Column names and categorical values closely follow the Citation Style Language (CSL) 1.0.2 specification. Names of people in non-Latin scripts are followed by a latinization in square brackets (e.g. В. С. Загороднов [V. S. Zagorodnov]) and non-English titles are followed by a translation in square brackets.

name type description

id (required) string Unique identifier constructed from the first author's lowercase, latinized, family name and the publication year, followed as needed by a lowercase letter to ensure uniqueness (e.g. Загороднов 1981 → zagorodnov1981a).

author (required) string Author names (optionally followed by their ORCID in parentheses) as a pipe-delimited list.

year (required) year Year of publication.

type (required) string Item type.- article-journal: Journal article- book: Book (if the entire book is relevant)- chapter: Book section- document: Document not fitting into any other category- dataset: Collection of data- map: Geographic map- paper-conference: Paper published in conference proceedings- personal-communication: Personal communication between individuals- speech: Presentation (talk, poster) at a conference- report: Report distributed by an institution- thesis: Thesis written to satisfy degree requirements- webpage: Website or page on a website

title string Item title.

url string URL (DOI if available).

language (required) string Language as ISO 639-1 two-letter language code.- de: German- en: English- fr: French- ko: Korean- ru: Russian- sv: Swedish- zh: Chinese

container_title string Title of the container (e.g. journal, book).

volume integer Volume number of the item or container.

issue string Issue number (e.g. 1) or range (e.g. 1-2) of the item or container, with an optional letter prefix (e.g. F1).

page string Page number (e.g. 1) or range (e.g. 1-2) of the item in the container.

version string Version number (e.g. 1.0) of the item.

editor string Editor names (e.g. of the containing book) as a pipe-delimited list.

collection_title string Title of the collection (e.g. book series).

collection_number string Number (e.g. 1) or range (e.g. 1-2) in the collection (e.g. book series volume).

publisher string Publisher name.

data/borehole.csv

Metadata about each borehole.

name type description

id (required) integer Unique identifier.

source_id (required) string Identifier of the source of the earliest temperature measurements. This is also the source of the borehole attributes unless otherwise stated in notes.

glacier_name (required) string Glacier or ice cap name (as reported).

glims_id string Global Land Ice Measurements from Space (GLIMS) glacier identifier.

location_origin (required) string Origin of location (latitude, longitude).- submitted: Provided in data submission- published: Reported as coordinates in original publication- digitized: Digitized from published map with complete axes- estimated: Estimated from published plot by comparing to a map (e.g. Google Maps, CalTopo)- guessed: Estimated with difficulty, for example by comparing elevation to a map (e.g. Google Maps, CalTopo)

latitude (required) number [degree] Latitude (EPSG 4326).

longitude (required) number [degree] Longitude (EPSG 4326).

elevation_origin (required) string Origin of elevation (elevation).- submitted: Provided in data submission- published: Reported as number in original publication- digitized: Digitized from published plot with complete axes- estimated: Estimated from elevation contours in published map- guessed: Estimated with difficulty, for example by comparing location (latitude, longitude) to a map of contemporary elevations (e.g. CalTopo, Google Maps)

elevation (required) number [m] Elevation above sea level.

label string Borehole name (e.g. as labeled on a plot).

date_min date (%Y-%m-%d) Begin date of drilling, or if not known precisely, the first possible date (e.g. 2019 → 2019-01-01).

date_max date (%Y-%m-%d) End date of drilling, or if not known precisely, the last possible date (e.g. 2019 → 2019-12-31).

drill_method string Drilling method.- mechanical: Push, percussion, rotary- thermal: Hot point, electrothermal, steam- combined: Mechanical and thermal

ice_depth number [m] Starting depth of ice. Infinity (INF) indicates that ice was not reached.

depth number [m] Total borehole depth (not including drilling in the underlying bed).

to_bed boolean Whether the borehole reached the glacier bed.

temperature_accuracy number [°C] Thermistor accuracy or precision (as reported). Typically understood to represent one standard deviation.

notes string Additional remarks about the study site, the borehole, or the measurements therein. Souces are referenced by their id.

curator string Names of people who added the data to the database, as a pipe-delimited list.

data/profile.csv

Date and time of each measurement profile.

name type description

borehole_id (required) integer Borehole identifier.

id (required) integer Borehole profile identifier (starting from 1 for each borehole).

source_id (required) string Source identifier.

measurement_origin (required) string Origin of measurements (measurement.depth, measurement.temperature).- submitted: Provided as numbers in data submission- published: Numbers read from original publication- digitized: Digitized from published plot(s) with Plot Digitizer

date_min date (%Y-%m-%d) Measurement date, or if not known precisely, the first possible date (e.g. 2019 → 2019-01-01).

date_max (required) date (%Y-%m-%d) Measurement date, or if not known precisely, the last possible date (e.g. 2019 → 2019-12-31).

time time (%H:%M:%S) Measurement time.

utc_offset number [h] Time offset relative to Coordinated Universal Time (UTC).

equilibrated boolean Whether temperatures have equilibrated following drilling.

notes string Additional remarks about the profile or the measurements therein. Sources are referenced by source.id.

data/measurement.csv

Temperature measurements with depth.

name type description

borehole_id (required) integer Borehole identifier.

profile_id (required) integer Borehole profile identifier.

depth (required) number [m] Depth below the glacier surface.

temperature (required) number [°C] Temperature.

This dataset represents the popular last names in the United States for White.

This dataset has been developed by the Australian Government as an authoritative source of indigenous location names across Australia. It is sponsored by the Spatial Policy Branch within the Department of Communications and managed solely by the Department of Human Services.

The dataset is designed to support the accurate positioning, consistent reporting, and effective delivery of Australian Government programs and services to indigenous locations.

The dataset contains Preferred and Alternate names for indigenous locations where Australian Government programs and services have been, are being, or may be provided. The Preferred name will always default to a State or Territory jurisdiction's gazetted name so the term 'preferred' does not infer that this is the locally known name for the location. Similarly, locational details are aligned, where possible, with those published in State and Territory registers.

This dataset is NOT a complete listing of all locations at which indigenous people reside. Town and city names are not included in the dataset. The dataset contains names that represent indigenous communities, outstations, defined indigenous areas within a town or city or locations where services have been provided.

Boys Names Registered in Ireland Data Resources (4) CSV Boys Names Registered in Ireland Preview Download JSON-STAT Boys Names Registered in Ireland Preview Download PX Boys Names Registered in Ireland Details Download XLSX Boys Names Registered in Ireland

Abstract

The dataset was derived by the Bioregional Assessment Programme. This dataset was derived from multiple datasets. You can find a link to the parent datasets in the Lineage Field in this metadata statement. The History Field in this metadata statement describes how this dataset was derived.

Asset database for the Hunter subregion on 24 February 2016 (V2.5) supersedes the previous version of the HUN Asset database V2.4 (Asset database for the Hunter subregion on 20 November 2015, GUID: 0bbcd7f6-2d09-418c-9549-8cbd9520ce18). It contains the Asset database (HUN_asset_database_20160224.mdb), a Geodatabase version for GIS mapping purposes (HUN_asset_database_20160224_GISOnly.gdb), the draft Water Dependent Asset Register spreadsheet (BA-NSB-HUN-130-WaterDependentAssetRegister-AssetList-V20160224.xlsx), a data dictionary (HUN_asset_database_doc_20160224.doc), and a folder (NRM_DOC) containing documentation associated with the Water Asset Information Tool (WAIT) process as outlined below. This version should be used for Materiality Test (M2) test.

The Asset database is registered to the BA repository as an ESRI personal goedatabase (.mdb - doubling as a MS Access database) that can store, query, and manage non-spatial data while the spatial data is in a separate file geodatabase joined by AID/ElementID.

Under the BA program, a spatial assets database is developed for each defined bioregional assessment project. The spatial elements that underpin the identification of water dependent assets are identified in the first instance by regional NRM organisations (via the WAIT tool) and supplemented with additional elements from national and state/territory government datasets. A report on the WAIT process for the Hunter is included in the zip file as part of this dataset.

Elements are initially included in the preliminary assets database if they are partly or wholly within the subregion's preliminary assessment extent (Materiality Test 1, M1). Elements are then grouped into assets which are evaluated by project teams to determine whether they meet the second Materiality Test (M2). Assets meeting both Materiality Tests comprise the water dependent asset list. Descriptions of the assets identified in the Hunter subregion are found in the "AssetList" table of the database.

Assets are the spatial features used by project teams to model scenarios under the BA program. Detailed attribution does not exist at the asset level. Asset attribution includes only the core set of BA-derived attributes reflecting the BA classification hierarchy, as described in Appendix A of "HUN_asset_database_doc_20160224.doc ", located in this filet.

The "Element_to_Asset" table contains the relationships and identifies the elements that were grouped to create each asset.

Detailed information describing the database structure and content can be found in the document "HUN_asset_database_doc_20160224.doc" located in this file.

Some of the source data used in the compilation of this dataset is restricted.

The public version of this asset database can be accessed via the following dataset: Asset database for the Hunter subregion on 24 February 2016 Public 20170112 v02 (https://data.gov.au/data/dataset/9d16592c-543b-42d9-a1f4-0f6d70b9ffe7)

Dataset History

OBJECTID VersionID Notes Date_

1 1 Initial database. 29/08/2014

3 1.1 Update the classification for seven identical assets from Gloucester subregion 16/09/2014

4 1.2 Added in NSW GDEs from Hunter - Central Rivers GDE mapping from NSW DPI (50 635 polygons). 28/01/2015

5 1.3 New AIDs assiged to NSW GDE assets (Existing AID + 20000) to avoid duplication of AIDs assigned in other databases. 12/02/2015

6 1.4 "(1) Add 20 additional datasets required by HUN assessment project team after HUN community workshop

       (2) Turn off previous GW point assets (AIDs from 7717-7810 inclusive) 

       (3) Turn off new GW point asset (AID: 0)

       (4) Assets (AIDs: 8023-8026) are duplicated to 4 assets (AID: 4747,4745,4744,4743 respectively) in NAM subregion . Their AID, Asset Name, Group, SubGroup, Depth, Source, ListDate and Geometry are using   

         values from that NAM assets.

      (5) Asset (AID 8595) is duplicated to 1 asset ( AID 57) in GLO subregion . Its AID, Asset Name, Group, SubGroup, Depth, Source, ListDate and Geometry are using values from that GLO assets.

      (6) 39 assets (AID from 2969 to 5040) are from NAM Asset database and their attributes were updated to use the latest attributes from NAM asset database 

     (7)The databases, especially spatial  database, were changed such as duplicated attributes fields in spatial data were removed and only ID field is kept. The user needs to join the Table Assetlist or Elementlist to 

        the spatial data"  16/06/2015

7 2 "(1) Updated 131 new GW point assets with previous AID and some of them may include different element number due to the change of 77 FTypes requested by Hunter assessment project team

      (2) Added 104 EPBC assets, which were assessed and excluded by ERIN

      (3) Merged 30 Darling Hardyhead assets to one (asset AID 60140) and deleted another 29 

      (4) Turned off 5 assets from community workshop (60358 - 60362) as they are duplicated to 5 assets from 104 EPBC excluded assets

     (5) Updated M2 test results

     (6) Asset Names (AID: 4743 and 4747) were changed as requested by Hunter assessment project team (4 lower cases to 4 upper case only). Those two assets are from Namoi asset database and their asset names 

       may not match with original names in Namoi asset database.

     (7)One NSW WSP asset (AID: 60814) was added in as requested by Hunter assessment project team. The process method (without considering 1:M relation) for this asset is not robust and is different to other NSW 

      WSP assets. It should NOT use for other subregions. 

     (8) Queries of Find_All_Used_Assets and Find_All_WD_Assets in the asset database can be used to extract all used assts and all water dependant assts" 20/07/2015

8 2.1 "(1) There are following six assets (in Hun subregion), which is same as 6 assets in GIP subregion. Their AID, Asset Name, Group, SubGroup, Depth, Source and ListDate are using values from GIP assets. You will

         not see AIDs from AID_from_HUN in whole HUN asset datable and spreadsheet anymore and you only can see AIDs from AID_from_GIP ( Actually (a) AID 11636 is GIP got from MBC (B) only AID, Asset Name 

         and ListDate are different and changed)

      (2) For BA-NSB-HUN-130-WaterDependentAssetRegister-AssetList-V20150827.xlsx, (a) Extracted long ( >255 characters) WD rationale for 19 assets (AIDs:  

         8682,9065,9073,9087,9088,9100,9102,9103,60000,60001,60792,60793,60801,60713,60739,60751,60764,60774,60812 ) in tab "Water-dependent asset register" and 37 assets (AIDs: 

         5040,8651,8677,8682,8650,8686,8687,8718,8762,9094,9065,9067,9073,9077,9081,9086,9087,9088,9100,9102,9103,60000,60001,60739,60742,60751,60713,60764,60771,

         60774,60792,60793,60798,60801,60809,60811,60812) in tab "Asset list" in 1.30 Excel file (b) recreated draft BA-NSB-HUN-130-WaterDependentAssetRegister-AssetList-V20150827.xlsx 

      (3) Modified queries (Find_All_Asset_List and Find_Waterdependent_asset_register) for (2)(a)"  27/08/2015

9 2.2 "(1) Updated M2 results from the internal review for 386 Sociocultural assets

      (2)Updated the class to Ecological/Vegetation/Habitat (potential species distribution) for assets/elements from sources of WAIT_ALA_ERIN, NSW_TSEC, NSW_DPI_Fisheries_DarlingHardyhead"  8/09/2015

10 2.3 "(1) Updated M2 results from the internal review

           \* Changed "Assessment team do not say No" to "All economic assets are by definition water dependent"

          \* Changed "Assessment team say No" : to "These are water dependent, but excluded by the project team based on intersection with the PAE is negligible"

          \* Changed "Rivertyles" to "RiverStyles""  22/09/2015

11 2.4 "(1) Updated M2 test results for 86 assets from the external review

      (2) Updated asset names for two assets (AID: 8642 and 8643) required from the external review

      (3) Created Draft Water Dependent Asset Register file using the template V5"  20/11/2015

12 2.5 "Total number of registered water assets was increased by 1 (= +2-1) due to:

              Two assets changed M2 test from "No" to "Yes" , but one asset assets changed M2 test from "Yes" to "No" 

             from the review done by Ecologist group." 24/02/2016

Dataset Citation

Bioregional Assessment Programme (2015) Asset database for the Hunter subregion on 24 February 2016. Bioregional Assessment Derived Dataset. Viewed 13 March 2019, http://data.bioregionalassessments.gov.au/dataset/a39290ac-3925-4abc-9ecb-b91e911f008f.

Dataset Ancestors

• Derived From GW Element Bores with Unknown FTYPE Hunter NSW Office of Water 20150514

• Derived From Travelling Stock Route Conservation Values

• Derived From Spatial Threatened Species and Communities (TESC) NSW 20131129

• Derived From NSW Wetlands

• Derived From Climate Change Corridors Coastal North East NSW

*

This is the latest version of the dataset initially published to GBIF by the Invasive Species Specialist Group (ISSG) on behalf of the U.S. Geological Survey on October 12, 2020, at https://www.gbif.org/dataset/6b64ef7e-82f7-47a3-8ddb-ec6794ea07d6. Like that checklist, this version presents validated and verified national checklists of introduced (alien) and invasive alien species at the sub-country level. The other two related checklists for the United States, also newly published separately as V2.0, are for the States of Alaska and Hawaii.

Differences between two previous versions and ver.2.0, 2022 (this dataset): SIZE: the first version V1.0 - 5,006 accepted names (arthropods were not included); the previous version - 8,654 accepted names and two unranked hybrids; ver.2.0, 2022 (this dataset) - 8,525 accepted names and two unranked hybrids. OTHER DIFFERENCES: the previous version provided: a broader inclusion of arthropods; approximate dates of introduction (where available); 4,693 references; improved disambiguation of scientific names; biocontrol species information (where applicable); taxonomic synonyms, where available, in taxonRemarks field; unique occurrenceIDs; no habitat information; ver.2.0, 2022 (this dataset) adds pathway and habitat information, where available, more precise management of names and synonyms (and so is smaller than the previous version), and additional data on approximate dates of introduction.

OVERVIEW: Introduced (non-native) species that becomes established may eventually become invasive, so tracking introduced species provides a baseline for effective modeling of species trends and interactions, geospatially and temporally. The umbrella dataset, called United States Register of Introduced and Invasive Species (US-RIIS), is comprised of three lists, one each for Alaska (AK, with 545 records), Hawaii (HI, with 5,628 records), and the conterminous (or lower 48) United States (L48, with 8,527 records, this dataset). Each list includes introduced (non-native), established (reproducing) taxa that: are, or may become, invasive (harmful) in the locality; are not known to be harmful there; and/or have been used for biological control in the locality.

To be included in the Global Register of Introduced and Invasive Species - United States (Contiguous), or GRIIS-L48 (with L48 meaning the Lower 48 Conterminous United States), a taxon must be non-native everywhere in the locality and established (reproducing) anywhere in the locality. Native pest species are not included.

Each record has information on taxonomy, a vernacular name, establishment means designation (introduced unintentionally, or assisted colonization), degree of establishment (established, invasive, or widespread invasive), hybrid status, pathway of introduction (where available), habitat (where available), whether a biocontrol species, dates of introduction (where available; currently 46% of the records for the conterminous United States), associated taxa (where applicable), native and introduced distributions (where available), and citations for the authoritative source(s) from which this information is drawn. The umbrella dataset US-RIIS builds on a previous dataset, A Comprehensive List of Non-Native Species Established in Three Major Regions of the U.S.: Version 3.0 (Simpson et al., 2020, https://doi.org/10.5066/p9e5k160).

There are 14,700 records in the master list (USRIISv2_MasterList) and 12,571 unique scientific names. The list is derived from more than 5,800 authoritative sources (USRIISv2_AuthorityReferences) and was reviewed by (or based on input from) more than 30 taxonomic experts and invasive species scientists.

Many thanks to these reviewers and contributors: Coauthors Pam Fuller (USGS Emeritus), Kevin Faccenda (University of Hawaii), Neal Evenhuis (Bishop Museum), Janis Matsunaga (Hawaii Department of Agriculture), and Matt Bowser (US-Fish and Wildlife Service); contributors Rachael Blake (data science), National Socio-Environmental Synthesis Center (SESYNC); M. Lourdes Chamorro (Curculionidae), USDA-ARS Entomology; Meghan C. Eyler (data reviewer), US Fish & Wildlife Service; Danielle Froelich (Hawaiian botany), SWCA Environmental Consultants; Thomas Henry (Heteroptera), USDA-ARS Entomology; Sam James (Annelida), Maharishi University; Nancy Khan (Hawaiian botany), Smithsonian Institution; Alex Konstantinov (Chrysomelidae), USDA-ARS Entomology; Andrew P. Landsman (Arachnida), National Park Service, C&O Canal National Historical Park; Christopher Lepczyk (Vertebrata), Auburn University; Sandy Liebhold (Coleoptera), USDA-FS; Steven Lingafelter (Cerambycidae), USDA-APHIS; Walter Meshaka (Herpetology), State Museum of Pennsylvania; Gary L. Miller (Aphididae), USDA-ARS Entomology; Allen Norrbom (Tephritidae), USDA-ARS Entomology; Shyama Pagad (global invasive species), IUCN SSC Invasive Species Specialists' Group; John Reynolds (Annelida), Oligochaetology Laboratory; Alexander Salazar (Lycosidae), Miami University, Ohio; Elizabeth A. Sellers (data manager), USGS; Derek Sikes (Alaskan invertebrates), University of Alaska; Bruce A. Snyder (Annelida), Georgia College and State University; Alma Solis (Pyralid moths), USDS-ARS at the Smithsonian Institution; Rebecca Turner (data manager), Scion Inc., New Zealand; Darrell Ubick (Arachnida), Cal Academy; Warren Wagner (Hawaiian botany), Smithsonian Institution; Mark Wetzel (Annelida), Illinois Natural History Survey; and James D. Young (Lepidoptera), USDA-APHIS-PPQ-PHP. Our apologies to the many contributing experts we may have inadvertently omitted.

Queensland Top 100 Baby Names

The Learning Resources Database is a catalog of interactive tutorials, videos, online classes, finding aids, and other instructional resources on National Library of Medicine (NLM) products and services. Resources may be available for immediate use via a browser or downloadable for use in course management systems

Dataset Description

It contains 520 rows and 13 variables as listed below - - Resource ID : Alphanumeric identifier - Resource Name : Title of the resource - Resource URL : Link of the resource - Description : Brief explanation on the reource - Archived : Flagged as False for all data points - Format : Format of the resource ex. HTML, PDF, MP4 video , MS Word, Powerpoint etc. - Type : Type of the resource ex Webinar, document, tutorial, slides etc. - Runtime : Runtime of the resource - Subject Areas : Topic covered in reource - Authoring Organization : Name of the Authoring Organization - Intended Audiences : Profile of the intended audience - Record Modified : Timestamp info on record last modification - Resource Revised : Timestamp info on resource last modified

As of June 2024, the most popular database management system (DBMS) worldwide was Oracle, with a ranking score of 1244.08; MySQL and Microsoft SQL server rounded out the top three. Although the database management industry contains some of the largest companies in the tech industry, such as Microsoft, Oracle and IBM, a number of free and open-source DBMSs such as PostgreSQL and MariaDB remain competitive. Database Management Systems As the name implies, DBMSs provide a platform through which developers can organize, update, and control large databases. Given the business world’s growing focus on big data and data analytics, knowledge of SQL programming languages has become an important asset for software developers around the world, and database management skills are seen as highly desirable. In addition to providing developers with the tools needed to operate databases, DBMS are also integral to the way that consumers access information through applications, which further illustrates the importance of the software.