Skip to content

Commit 9361fa9

Browse files
maximilianimaximiliani
authored
Merge pull request #201 from kit-data-manager/dev
Dev
2 parents ed51e66 + b1cd8de commit 9361fa9

File tree

9 files changed

+3148
-4391
lines changed

9 files changed

+3148
-4391
lines changed

‎.pre-commit-config.yaml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ repos:
55
rev: v3.2.0
66
hooks:
77
- id: trailing-whitespace
8-
- id: end-of-file-fixer
98
- id: check-yaml
109
- id: check-added-large-files
1110
- repo: https://github.com/Materials-Data-Science-and-Informatics/somesy

‎.storybook/main.ts

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,5 +9,8 @@ const config = {
99
docs: {
1010
autodocs: 'tag',
1111
},
12+
core: {
13+
disableTelemetry: true,
14+
}
1215
};
1316
export default config;

‎.storybook/preview-head.html

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,12 @@
1-
<meta name="description" content="The pid-component is an easily extensible web component that can be used to display PIDs, ORCiDs, and possibly other identifiers in a user-friendly way. It is easily extensible to support other identifier types." key="desc" />
1+
<meta name="description" content="The pid-component is an easily extensible web component that can be used to display PIDs, ORCiDs, and possibly other identifiers in a user-friendly way. It is easily extensible to support other identifier types."/>
2+
<meta name="keywords" content="web component, pid, orcid, identifier, extensible, fairdo, opensource, github, npm, typescript, stencil"/>
3+
<meta name="author" content="KIT Data Manager"/>
4+
<meta property="og:title" content="Storybook - pid-component"/>
5+
<meta property="og:description" content="The pid-component is an easily extensible web component that can be used to display PIDs, ORCiDs, and possibly other identifiers in a user-friendly way. It is easily extensible to support other identifier types."/>
6+
<meta property="og:url" content="https://kit-data-manager.github.io/pid-component">
7+
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
28
<title>Storybook - pid-component</title>
3-
<!--<script type='module' src='https://unpkg.com/@kit-data-manager/pid-component'></script>-->
9+
<script type='module' src='https://unpkg.com/@kit-data-manager/pid-component'></script>
410

511
<!--For testing only-->
6-
<script type='module' src='./dist/pid-component/pid-component.esm.js'></script>
12+
<!--<script type='module' src='./dist/pid-component/pid-component.esm.js'></script>-->

‎CITATION.cff

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@ cff-version: 1.2.0
22
message: If you use this software, please cite it using these metadata.
33
type: software
44
title: '@kit-data-manager/pid-component'
5-
abstract: The PID-Component is a web component that can be used to display PIDs, ORCiDs,
6-
and possibly other identifiers in a user-friendly way. It is easily extensible to
7-
support other identifier types.
5+
abstract: The PID-Component is a web component that can be used to evaluate and display
6+
FAIR Digital Objects, PIDs, ORCiDs, and possibly other identifiers in a user-friendly
7+
way. It is easily extensible to support other identifier types.
88
version: 0.1.0
99
keywords:
1010
- stencil

‎CODE_OF_CONDUCT.md

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, gender identity and expression, level of experience,
9+
education, socio-economic status, nationality, personal appearance, race,
10+
religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at {{ email }}. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
72+
73+
[homepage]: https://www.contributor-covenant.org

‎CONTRIBUTING.md

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
# Contributing
2+
3+
When contributing to this repository, please first discuss the change you wish to make via issue,
4+
email, or any other method with the owners of this repository before making a change.
5+
6+
Please note we have a code of conduct, please follow it in all your interactions with the project.
7+
8+
## Pull Request Process
9+
10+
1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
11+
2. State in the Pull Request details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and container parameters.
12+
3. Pull Requests are merged after successful review of at least one of the project owners.
13+
14+
## Code of Conduct
15+
16+
### Our Pledge
17+
18+
In the interest of fostering an open and welcoming environment, we as
19+
contributors and maintainers pledge to making participation in our project and
20+
our community a harassment-free experience for everyone, regardless of age, body
21+
size, disability, ethnicity, gender identity and expression, level of experience,
22+
nationality, personal appearance, race, religion, or sexual identity and
23+
orientation.
24+
25+
### Our Standards
26+
27+
Examples of behavior that contributes to creating a positive environment
28+
include:
29+
30+
- Using welcoming and inclusive language
31+
- Being respectful of differing viewpoints and experiences
32+
- Gracefully accepting constructive criticism
33+
- Focusing on what is best for the community
34+
- Showing empathy towards other community members
35+
36+
Examples of unacceptable behavior by participants include:
37+
38+
- The use of sexualized language or imagery and unwelcome sexual attention or advances
39+
- Trolling, insulting/derogatory comments, and personal or political attacks
40+
- Public or private harassment
41+
- Publishing others' private information, such as a physical or electronic address, without explicit permission
42+
- Other conduct which could reasonably be considered inappropriate in a professional setting
43+
44+
### Our Responsibilities
45+
46+
Project maintainers are responsible for clarifying the standards of acceptable
47+
behavior and are expected to take appropriate and fair corrective action in
48+
response to any instances of unacceptable behavior.
49+
50+
Project maintainers have the right and responsibility to remove, edit, or
51+
reject comments, commits, code, wiki edits, issues, and other contributions
52+
that are not aligned to this Code of Conduct, or to ban temporarily or
53+
permanently any contributor for other behaviors that they deem inappropriate,
54+
threatening, offensive, or harmful.
55+
56+
### Scope
57+
58+
This Code of Conduct applies both within project spaces and in public spaces
59+
when an individual is representing the project or its community. Examples of
60+
representing a project or community include using an official project e-mail
61+
address, posting via an official social media account, or acting as an appointed
62+
representative at an online or offline event. Representation of a project may be
63+
further defined and clarified by project maintainers.
64+
65+
### Enforcement
66+
67+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
68+
reported by contacting the project team at webmaster@datamanager.kit.edu. All
69+
complaints will be reviewed and investigated and will result in a response that
70+
is deemed necessary and appropriate to the circumstances. The project team is
71+
obligated to maintain confidentiality with regard to the reporter of an incident.
72+
Further details of specific enforcement policies may be posted separately.
73+
74+
Project maintainers who do not follow or enforce the Code of Conduct in good
75+
faith may face temporary or permanent repercussions as determined by other
76+
members of the project's leadership.
77+
78+
### Attribution
79+
80+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
81+
available at [http://contributor-covenant.org/version/1/4][version]
82+
83+
[homepage]: http://contributor-covenant.org
84+
[version]: http://contributor-covenant.org/version/1/4/

‎codemeta.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@
1818
}
1919
],
2020
"name": "@kit-data-manager/pid-component",
21-
"description": "The PID-Component is a web component that can be used to display PIDs, ORCiDs, and possibly other identifiers in a user-friendly way. It is easily extensible to support other identifier types.",
21+
"description": "The PID-Component is a web component that can be used to evaluate and display FAIR Digital Objects, PIDs, ORCiDs, and possibly other identifiers in a user-friendly way. It is easily extensible to support other identifier types.",
2222
"version": "0.1.0",
2323
"keywords": [
2424
"stencil",

0 commit comments

Comments
 (0)