scholarsportal / dataverse-data-explorer Goto Github PK

A tool for curating data by adding labels, groups, weights and other details to assist with informed reuse

TypeScript 72.81% JavaScript 1.59% HTML 20.97% CSS 4.49% Dockerfile 0.14%

dataverse curating-data angular statistics

dataverse-data-explorer's Introduction

Dataverse Data Explorer

The Data Curation Tool (DCT) allows data owners and curators to view summary statistics for variables and to create and edit variable-level metadata for any tabular file in a data set. This stand-alone component is built to complement The Dataverse Project. The Data Curation tool is integrated into dataverse for .tab files under the configure button.

The DCT is an Angular application.

A demo of the tool is available here; note that this Github pages demo is not recommended for use in a production environment: https://scholarsportal.github.io/Dataverse-Data-Explorer/?dfId=127759&siteUrl=https://borealisdata.ca.

Installation

Pre-Requisites

NodeJS (runtime for Angular and client)

For development, I recommend using a Node Version manager such as nvm or fnm. Otherwise, NodeJS can be found here.
Angular (client framework)

npm install -g @angular/cli

Integrating Data Explorer in your institution? See the Dataverse guide for more information about installing external tools.

Now to start development.

npm install
ng serve

Variable Selection Context

When a user selects a variables, navigates to another group, and makes another selection, the app holds the selection information for both contexts in which the selection in made. In simple terms the user does not have to worry about losing their selection when they change groups.

App State

The tool has a state divided into three distinct state groups.

The XML State is the final DDI file that will be uploaded to Dataverse.

The Dataset State contains information about operations being operated on the dataset (upload and download status), any extra information gained from an API call (variable cross tab data), as well as imported file information.

The UI state represents any UI changes, including any temporary visual changes to the dataset (invalid values in the chart modal).

Actions

dataverse-data-explorer's People

Contributors

Stargazers

Watchers

Forkers

lubitchv pdurbin djbrooke laurencehorton uncch-rdmc dans-labs renefgjr muhamed-al ericgrossi kkwen123 aadorian

dataverse-data-explorer's Issues

Upgrade Matomo

Limit of 10 groups added

Upgrade to Angular 16

build error on CentOS 8

$ ng build --prod --base-href <url>
Your global Angular CLI version (11.2.11) is greater than your local version (9.1.7). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
Schema validation failed with the following errors:
  Data path "" should NOT have additional properties(es5BrowserSupport).

Just curious if you've seen this build error before?

{"status":"ERROR","message":"Unknown reserved word: {localeCode}"}

When I try to use https://github.com/scholarsportal/Dataverse-Data-Curation-Tool/blob/9d14dde6ee0482d3dea63656f28bbe8ad1dba7e5/DataCuration.json I get the following error:

{"status":"ERROR","message":"Unknown reserved word: {localeCode}"}

Removing this fixed it:

 {
    "dvLocale": "{localeCode}"
 },

I believe localeCode is coming as part of IQSS/dataverse#6215 but it isn't here yet so it should probably be removed for now. 😄

docs: baseurl seems to want trailing slash

without it DCT renders a blank page.

Create local auto save feature

avoiding {"status":"ERROR","message":"scope is required."}

Hello! Please be advised that the next version of Dataverse (after 4.16) will require a "scope" of "file" for your manifest file to be loaded into Dataverse. In my testing of other tools, I've been putting "scope" right above "type", like this:

"scope": "file",
"type": "explore",

You don't need to worry about backward compatibility. Dataverse 4.16 and below will happily accept "scope". What we are trying to avoid is {"status":"ERROR","message":"scope is required."} on newer versions of Dataverse.

Add proportion

Consider showing the proportion (%age) as well as count. This could be a column to the right or left of count, or some other solution.

installation instructions needed

Please add installation instructions to the README, similar to https://github.com/scholarsportal/Dataverse-Data-Explorer#installation

Thanks!!

As I mentioned at IQSS/dataverse#5971 (comment) I added the Data Curation Tool to the list of external tools. This is what I wrote:

Data Curation Tool: a GUI for curating data by adding labels, groups, weights and other details to assist with informed reuse. See the README.md file at https://github.com/scholarsportal/Dataverse-Data-Curation-Tool for the installation instructions.

You are welcome to edit this text, of course. It hasn't been merged into "develop" yet. Right now the text is in lubitchv/dataverse#23 which I'm suggesting can be merged into IQSS/dataverse#5971

The idea is that the text above or something like it will appear in a future version of this page:

http://guides.dataverse.org/en/4.15/installation/external-tools.html#inventory-of-external-tools

That is to say, it would look something like this:

Dataset can't save if text is copied from PDF.

If the copied text includes a line break, something about that prevents it from saving.

Build Issues

Reported by Steven Winship via email

 
Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:79:19)
    at Object.createHash (node:crypto:139:10)
    at module.exports (/home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/webpack/lib/NormalModule.js:417:16)
    at /home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/webpack/lib/NormalModule.js:452:10
    at /home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/webpack/lib/NormalModule.js:323:13
    at /home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/loader-runner/lib/LoaderRunner.js:367:11
    at /home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/loader-runner/lib/LoaderRunner.js:203:19
    at VirtualFileSystemDecorator.readFile (/home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/@ngtools/webpack/src/virtual_file_system_decorator.js:46:13)
    at processResource (/home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/loader-runner/lib/LoaderRunner.js:202:11)
    at iteratePitchingLoaders (/home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/loader-runner/lib/LoaderRunner.js:158:10)
    at iteratePitchingLoaders (/home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/loader-runner/lib/LoaderRunner.js:165:10)
    at /home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/loader-runner/lib/LoaderRunner.js:176:18
    at loadLoader (/home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/loader-runner/lib/loadLoader.js:47:3)
    at iteratePitchingLoaders (/home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
    at runLoaders (/home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/loader-runner/lib/LoaderRunner.js:365:2)
    at NormalModule.doBuild (/home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/webpack/lib/NormalModule.js:295:3)
    at NormalModule.build (/home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/webpack/lib/NormalModule.js:446:15)
    at Compilation.buildModule (/home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/webpack/lib/Compilation.js:739:10)
    at /home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/webpack/lib/Compilation.js:981:14
    at /home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/webpack/lib/NormalModuleFactory.js:409:6
    at /home/rocky/Dataverse-Data-Curation-Tool-1.1/node_modules/webpack/lib/NormalModuleFactory.js:155:13 {
  opensslErrorStack: [
    'error:03000086:digital envelope routines::initialization error',
    'error:0308010C:digital envelope routines::unsupported'
  ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}