-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #131 from DLFMetadataAssessment/issue#130
Updating with content from Sandbox for DLF Forum 2022
- Loading branch information
Showing
235 changed files
with
4,762 additions
and
4,625 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,70 @@ | ||
--- | ||
name: Metadata Resource Submission | ||
about: Submit documents to the DLF AIG Metadata Application Profile Clearinghouse | ||
Project. Complete the form in the "Write" tab, use the "Preview" tab to review, | ||
and then click "Submit new issue". | ||
title: New MAP Clearinghouse resource | ||
labels: MAP Clearinghouse submission | ||
assignees: '' | ||
|
||
--- | ||
|
||
### Instructions | ||
|
||
This form will allow you to submit your institution's application profiles, mappings, crosswalks and metadata code as digital files to the Clearinghouse project[1]. The MAP Clearinghouse is a project of the Digital Library Federation (DLF) Assessment Interest Group (AIG) Metadata Assessment Working Group[2]. The Metadata Assessment Working Group aims to build guidelines, best practices, tools and workflows around the evaluation and assessment of (mostly, descriptive) metadata used by and for digital libraries and repositories. | ||
|
||
[1] https://dlfmetadataassessment.github.io/MetadataSpecsClearinghouse/ | ||
[2] https://dlfmetadataassessment.github.io/ | ||
|
||
The following information will be used to describe your document(s) when on the Clearinghouse website. Please be aware that if you do not complete the mandatory portions of this submission form, we may not be able to include your document(s) in the Clearinghouse. | ||
|
||
Within each section, replace "Type your answer here" with the requested information. You may use Markdown to format your text. Use the "Preview" tab to review, and then click "Submit new issue" to complete your submission. | ||
|
||
### Institution Name (required) | ||
|
||
**[Type your answer here]** | ||
|
||
### Description of Institution (optional) | ||
|
||
**[Type your answer here]** | ||
|
||
### Resource Name (required) | ||
|
||
**[Type your answer here]** | ||
|
||
### Resource Type (required) | ||
|
||
*Select one. How to fill out*: `- [x] Best practice` | ||
|
||
- [ ] Metadata application profile | ||
- [ ] Metadata mapping | ||
- [ ] Best practice | ||
- [ ] Metadata schema | ||
|
||
### Description of the Resource (optional) | ||
|
||
*Please tell us about the document(s) in a handful of sentences -- what is it used for? Why does it exist? If you have a lot to say about your doc(s) (more than one or two sentences), please consider zipping your submission with a README file.* | ||
|
||
**[Type your answer here]** | ||
|
||
### Resource Version and Date (optional) | ||
|
||
*Please tell us if there is a version number associated with the document(s) and the date when it was released.* | ||
|
||
**[Type your answer here]** | ||
|
||
### Contact Information (required) | ||
|
||
*Please provide a name and email address for a person whom the Metadata Assessment Working Group can contact with any questions about this submission.* | ||
|
||
**[Type your answer here]** | ||
|
||
### Is there any other information you would like to provide? (optional) | ||
|
||
**[Type your answer here]** | ||
|
||
### Provide File Attachment (required) | ||
|
||
*Please attach your file(s) using the drag and drop or selection method described at the end of this box.* | ||
|
||
*If your content exceeds 10 MB, or if you have any questions or feedback, please contact the Metadata Assessment Working Group at [email address].* |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,27 +1,4 @@ | ||
# Folder view configuration files | ||
.DS_Store | ||
Desktop.ini | ||
|
||
# Thumbnail cache files | ||
._* | ||
Thumbs.db | ||
|
||
# Files that might appear on external disks | ||
.Spotlight-V100 | ||
.Trashes | ||
|
||
# Compiled Python files | ||
*.pyc | ||
|
||
# Compiled C++ files | ||
*.out | ||
|
||
# Application specific files | ||
venv | ||
bower_components | ||
node_modules | ||
#_site/ | ||
#.sass-cache/ | ||
_site | ||
.sass-cache | ||
.jekyll-metadata | ||
.brackets.json | ||
Gemfile | ||
Gemfile.lock |
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-43.3 KB
.sass-cache/361b8f43efc4363cbd9a8a5cc41b098a7f33ed80/_syntax-highlighting.scssc
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-43.2 KB
.sass-cache/42dbfc36729841dc31c1c2b34e528cf31f13e885/_syntax-highlighting.scssc
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-43.3 KB
.sass-cache/4ad02e788f70645884bd7dd75dafc9a71c9a8b68/_syntax-highlighting.scssc
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-38.2 KB
.sass-cache/57f02842d63c075d0bda27cc161e923e27ee50e9/_general.scssc
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-43.2 KB
.sass-cache/6d13b897a9f8297c7184fb7eb3e41e7508bcf9f7/_syntax-highlighting.scssc
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-43.3 KB
.sass-cache/9297ed1969bb463c15b5d5b5e95ae7f3df3949cf/_syntax-highlighting.scssc
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-43.3 KB
.sass-cache/beb2562e3b131156d0d166771eb27259be69c829/_syntax-highlighting.scssc
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-43.2 KB
.sass-cache/ee9626a4262fdc03125a64e14288da61f083f686/_syntax-highlighting.scssc
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-4.76 KB
.sass-cache/ef01740096f0f55b4f0cb7efc8535fcce97d51ba/_functions.scssc
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-2.85 KB
.sass-cache/ef01740096f0f55b4f0cb7efc8535fcce97d51ba/_typography.scssc
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-43.2 KB
.sass-cache/f6ebf4d15285d92540b44b0bc7e7fe89bb6ec6a6/_syntax-highlighting.scssc
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,7 @@ | ||
source "https://rubygems.org" | ||
|
||
gem "github-pages" | ||
gem 'rack-jekyll' | ||
gem "github-pages", group: :jekyll_plugins | ||
|
||
gem "jekyll-redirect-from", "~> 0.16.0" | ||
|
||
gem "webrick", "~> 1.7" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.