0.5.7 • Published 1 year ago

data-metrics-badge v0.5.7

Weekly downloads
101
License
MIT
Repository
github
Last release
1 year ago

Published on webcomponents.org npm version npm.io Build Status

Data Metrics Badge

The Data Metrics Badge provides an open and easy way to display the number of citations and usage that your research datasets and resources have received.

The Data Metrics Badge was created as part of the PARSEC, Building New Tools for Data Sharing and Reuse through a Transnational Investigation of the Socioeconomic Impacts of Protected Areas.

The Data Metrics Badge is a an easy way to embed usage and citations metrics from DataCite Services on your repository landing page. Usage statistics are processed according to the Code of Practice for Research Data. Citation statistics are collected via the DataCite and Crossref EventData Service.

Browsers support

IE / EdgeFirefoxChromeSafariOpera
Edgelast 2 versionslast 2 versionslast 2 versionslast 2 versions

One will need to include the web-components-loader for Edge and IE compatibility.

  <script src="https://unpkg.com/browse/@webcomponents/webcomponentsjs@2.0.0/webcomponents-loader.js"></script>

Installation and Usage

Getting set up with a Data Metrics Badge is a straightforward process – just add the following code to the HTML of your website wherever you want the Data Metrics Badge to appear:

<script src="https://unpkg.com/vue"></script>
<script src="https://cdn.jsdelivr.net/npm/data-metrics-badge/dist/data-metrics-badge.min.js"></script>


<body>
  <data-metrics-badge doi="10.7272/q6g15xs4"></data-metrics-badge>
</body>

There is also a live demo.

Project setup

yarn install

Compiles and hot-reloads for development

yarn serve

Compiles and minifies for production

yarn build --target wc --name data-metrics-badge 'src/components/DataMetricsBadge.vue'

npm version patch -m "Upgrade to %s for reasons"

Run your tests

yarn test:unit tests/

Lints and fixes files

npm run lint

Publishing to NPMJS.com

After merging changes via a pull request, manually run the bump-version github action, using the next version number after the last released version. The bump-version action will set the correct version in package.json, commit it, and create a release tag. Then, create a release using that tag.

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

License

MIT

Customize configuration

See Configuration Reference.

0.5.7

1 year ago

0.5.4

2 years ago

0.5.5

2 years ago

0.5.3

3 years ago

0.5.2

4 years ago

0.5.0

4 years ago

0.5.1

4 years ago

0.4.31

4 years ago

0.4.28

4 years ago

0.4.29

4 years ago

0.4.27

4 years ago

0.4.30

4 years ago

0.4.26

4 years ago

0.4.24

4 years ago

0.4.23

4 years ago

0.4.22

4 years ago

0.4.20

4 years ago

0.4.21

4 years ago

0.4.19

4 years ago

0.4.18

4 years ago

0.4.17

4 years ago

0.4.16

4 years ago

0.4.15

4 years ago

0.4.14

4 years ago

0.4.13

4 years ago

0.4.12

4 years ago

0.4.11

4 years ago

0.4.10

4 years ago

0.4.9

4 years ago

0.4.8

4 years ago

0.4.7

4 years ago

0.4.6

4 years ago

0.4.5

4 years ago

0.4.4

4 years ago

0.4.3

4 years ago

0.4.1

4 years ago

0.4.2

4 years ago

0.4.0

4 years ago

0.2.4

4 years ago

0.2.3

4 years ago

0.2.2

4 years ago

0.2.1

5 years ago

0.2.0

5 years ago

0.1.6

5 years ago

0.1.5

5 years ago

0.1.4

5 years ago

0.1.3

5 years ago

0.1.1

5 years ago

0.1.0

5 years ago