Ticket tracking and initial efforts at deliverables for the File Sets WG
Working Group Home Page: https://wiki.duraspace.org/display/hydra/PCDM+FileSets+Working+Group
done when
Background: 4th use case currently states:
pcdmuse terms are used to designate the role of each File in a FileSet
Done when: 1 or more diagrams are displayed (or linked to) from the charter homepage that clearly illustrate examples for the 4th stated use case.
done when the value of the pcdm:use property of a pcdm:File can be customized
Rationale: The first use case listed in the charter is currently worded as "A FileSet is formally defined in PCDM as an aggregation of Files derived from the same source", but per our most recent meeting, the consensus was that we don't need a specific FileSet object in the PCDM ontology.
If we are going to "formally" define what a FileSet is, we need to figure out where that formal definition will live. Otherwise, we may be able to get rid of this use case altogether. Thoughts?
Background: The second use case currently states:
A FileSet becomes the designated place to represent digital content and can have descriptive metadata about that content directly attached to it; technical metadata are related to the individual Files
Done when: 1 or more diagrams are displayed (or linked to) from the charter homepage that clearly illustrate examples for the second stated use case.
CircleCI can be used to prevent the recreation of the old default branch name. This helps preserve automatic redirection to the new default branch, and prevents accidentally re-adding the legacy branch from a stale fork. If CircleCI is not integrated with this repository, please do the following:
Add information to the README explicitly defining branch naming conventions accepted for this repository (instructions in this GitHub gist).
Optionally, integrate CircleCI with your repository (see GitHub documentation from CircleCI), and add a test to fail when a branch called master is present (instructions in this GitHub gist).
Git's default "master" branch derives from "master/slave" jargon which perpetuates systemic racist language and systems (see email Replacing "master" reference in git branch names). To uphold our Code of Conduct, we must move away from the term "master" in our technical language (as well as words like blacklist or whitelist).
Background: The first use case currently states:
A FileSet is formally defined in PCDM as an aggregation of Files derived from the same source, containing different formats or subsets of the same content (original, master, intermediate, access, thumbnail etc.)
Done when: 1 or more diagrams are displayed (or linked to) from the charter homepage that clearly illustrate examples for the first stated use case.
The Renaming Branch Working Group is in the process of renaming the default branch from master to main in Samvera and Samvera-Labs repos. This brings repositories into compliance with the Samvera Community Code of Conduct (https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Code+of+Conduct) and language recommendations (https://github.com/samvera/maintenance/blob/master/templates/CONTRIBUTING.md#language).
This issue will be complete when the master has been renamed to main.
Related issues will have a title beginning with RENAME.
Background: The 3rd use case currently states:
Technical metadata as an explicit XML file can be stored in the same FileSet as the file from which the technical metadata is produced
Done when: 1 or more diagrams are displayed (or linked to) from the charter homepage that clearly illustrate examples for the 3rd stated use case.
Add the following branch renaming language to the README for this repository.
## Contributing
If you're working on PR for this project, create a feature branch off of `main`.
This repository follows the [Samvera Community Code of Conduct](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Code+of+Conduct) and [language recommendations](https://github.com/samvera/maintenance/blob/master/templates/CONTRIBUTING.md#language). Please ***do not*** create a branch called `master` for this repository or as part of your pull request; the branch will either need to be removed or renamed before it can be considered for inclusion in the code base and history of this repository.
Git's default "master" branch derives from "master/slave" jargon which perpetuates systemic racist language and systems (see email Replacing "master" reference in git branch names). To uphold our Code of Conduct, we must move away from the term "master" in our technical language (as well as words like blacklist or whitelist).
This repository’s default branch has already been renamed using GitHub’s renaming tool. Links that reference the old branch name are automatically forwarded to the new default branch. But string references are not automatically updated.
Check this repository for hard-coded string references to the legacy “master” default branch and update them to the new default branch name “main.”
Important places to check include, but are not limited to:
NOTE: READMEs, wikis, and other documentation are important to update to avoid confusion and correct errors in long lasting documentation.
Less common places to check:
NOTE: String references to themaster branch in Issues, PRs, and code are uncommon. Also Issues and PRs are temporal in nature, making it less critical to update those occurrences.
Git's default "master" branch derives from "master/slave" jargon which perpetuates systemic racist language and systems (see email Replacing "master" reference in git branch names). To uphold our Code of Conduct, we must move away from the term "master" in our technical language (as well as words like blacklist or whitelist).
done when all working group members are on the team
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.