Science Score: 54.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
✓Academic publication links
Links to: zenodo.org -
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (11.8%) to scientific vocabulary
Repository
The core data of the Iconclass Classification System
Basic Info
- Host: GitHub
- Owner: iconclass
- License: cc0-1.0
- Language: Python
- Default Branch: main
- Size: 26.1 MB
Statistics
- Stars: 14
- Watchers: 3
- Forks: 7
- Open Issues: 8
- Releases: 1
Metadata Files
README.md
ICONCLASS
Please use the following to cite:
H. van de Waal, Iconclass, an iconographic classification system. Completed and edited by L.D. Couprie, E. Tholen & G. Vellekoop. (Amsterdam, 1972-1985). online edition by E. Posthumus & J.P.J. Brandhorst, 2024. https://iconclass.org/
A multilingual subject classification system for cultural content For more information see: http://www.iconclass.org/
Made by Hans Brandhorst jpjbrand@xs4all.nl & Etienne Posthumus eposthumus@gmail.com
...with lots of support from a global cast of many, many people since 1972.
Data file
This repository contains the main data files for the ICONCLASS system. It is a collection of simple structured text files, dating back in concept to the late nineties of the previous century.
Structure
The structure is determined by the file notations.txt.
For example, the file looks like:
N 1
C 10
; 11
; 12
; 13
; 14
$
N 10
$
This is a chunk of data (each chunk is separated by a single $ character on its own line)
The first part of a line, up to the first space, is the field name. If there are multi-valued fields, in other words, more than one value for a field, it is listed on a different line starting with a ; character,followed by a space and the field value. The above snippet, is roughly equivalent to the following JSON value:
javascript
[
{N: "1",
C: ["10", "11", "12", "13", "14"]},
{N: "10}
]
Why not use a standard Knowledge Management System?
You might wonder why we can not simply use a standard system to manage vocabularies or classification systems. If IC has a SKOS version, surely we can just use a SKOS editor?
Alas, no. The "base" ICONCLASS system has around 40K nodes arranged in a tree. But then there are several "sub-trees" that are switched on and off at various parts of the base tree. These so-called "keys" in the IC causes an explosion to more than 1 million nodes in the system, which would make it very tricky to maintain in a traditional system.
A further complication is the use of WITH-NAMES placeholders in tree, also known as bracketed text. These notations look like 11H(...) where the ... can be filled in with any valid entry that makes sense to the user using that particular node in the tree. In the example, 11H(...) are male saints, so that could be 11H(JOHN) - but this could be in any language or variant. In the printed volumes for IC, several entries were already filled in as a convenience, and over the years some items have been added to the "official" list.
This also causes a problem when we create static dumps of the IC system, for example in RDF as it creates very large files.
Owner
- Name: iconclass
- Login: iconclass
- Kind: organization
- Repositories: 3
- Profile: https://github.com/iconclass
Citation (CITATION.cff)
cff-version: 1.2.0
title: ICONCLASS
message: >-
If you use this dataset, please cite it using the metadata
from this file.
type: dataset
authors:
- family-names: Posthumus
name-particle: E
orcid: "https://orcid.org/0000-0002-0006-7542"
- name-particle: JPJ
family-names: Brandhorst
orcid: "https://orcid.org/0000-0001-8403-3552"
url: "https://iconclass.org/"
license: CC0-1.0
GitHub Events
Total
- Watch event: 4
- Issue comment event: 2
- Push event: 32
- Pull request event: 5
- Fork event: 1
- Create event: 1
Last Year
- Watch event: 4
- Issue comment event: 2
- Push event: 32
- Pull request event: 5
- Fork event: 1
- Create event: 1
Issues and Pull Requests
Last synced: 10 months ago
All Time
- Total issues: 0
- Total pull requests: 1
- Average time to close issues: N/A
- Average time to close pull requests: 2 days
- Total issue authors: 0
- Total pull request authors: 1
- Average comments per issue: 0
- Average comments per pull request: 0.0
- Merged pull requests: 1
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 1
- Average time to close issues: N/A
- Average time to close pull requests: 2 days
- Issue authors: 0
- Pull request authors: 1
- Average comments per issue: 0
- Average comments per pull request: 0.0
- Merged pull requests: 1
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
- mathiaszinnen (2)
- bkiers (1)
- epoz (1)
Top Labels
Issue Labels
Pull Request Labels
Dependencies
- actions/checkout v3 composite
- actions/upload-artifact v3 composite