360 KB: Data Planet from SAGE Publications: Database Names Change -- Nov, 2023
What is happening to the names of Data Planet databases?
The provider SAGE Publications has changed the name of Data Planet databases.
Therefore, we will be changing the database names in the Knowledgebase. The content of the databases, and the database IDs, will remain the same.
This change will take effect on November 10, 2023:
| DB Code | Database Name Before November 10, 2023 | Database Name After November 10, 2023 |
|---|---|---|
| ADQXP | Data Planet Foundations | Sage Data Foundations |
| ACBVO | Data Planet Statistical Datasets CORE | Sage Data CORE |
| AFODN | Data Planet Statistical Datasets Premium: China Data Center (National/Subnational) | Sage Data Premium: China Data Center (National/Subnational) |
| AGBPI | Data Planet Statistical Datasets Premium: Claritas Consumer Profiles | Sage Data Premium: Claritas Consumer Profiles |
| ADYGP | Data Planet Statistical Datasets Premium: Claritas Financial and Consumer Clout | Sage Data Premium: Claritas Financial and Consumer Clout |
| AEAEB | Data Planet Statistical Datasets Premium: Data Axle Historical Canadian Business | Sage Data Premium: Data Axle Historical Canadian Business |
| ABLFR | Data Planet Statistical Datasets Premium: Data Axle Historical US Business | Sage Data Premium: Data Axle Historical US Business |
| AAKKX | Data Planet Statistical Datasets Premium: Data Axle Historical US Residential | Sage Data Premium: Data Axle Historical US Residential |
| AANZH | Data Planet Statistical Datasets Premium: EASI Market Planner | Sage Data Premium: EASI Market Planner |
| ADZPW | Data Planet Statistical Datasets Premium: Woods and Poole | Sage Data Premium: Woods and Poole |
Actions you may need to take:
- If you are a 360 MARC Updates client and have requested the custom specification that adds the database name as it appears in the Client Center/Intota to MARC records, you can expect to see some change records when you get your MARC records after November 10, 2023.
- If your library uses a third-party service (such as EBSCO A-Z, etc.), custom scripts to manage data, or other non-ProQuest tools that require the database name to function, you should note the change in ProQuest's database name in order to retain the proper relationship/mapping between those tools.
- Article last edited: 25-Oct-2023