issues
search
DILCISBoard
/
E-ARK-SIP
E-ARK SIP specification
https://earksip.dilcis.eu/
Creative Commons Attribution 4.0 International
7
stars
6
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Link to extension schema
#39
karinbredenberg
closed
4 years ago
4
Chapter 3.4
#38
karinbredenberg
closed
5 years ago
3
SIP32
#37
karinbredenberg
closed
4 years ago
2
SIP10
#36
karinbredenberg
closed
5 years ago
3
SIP16
#35
karinbredenberg
closed
5 years ago
5
Add script that generates the PDF version of the Spec
#34
jmaferreira
closed
4 years ago
4
Removal of text duplication
#33
karinbredenberg
closed
5 years ago
1
Addition of vocabularyOAISPackageType
#32
karinbredenberg
closed
5 years ago
0
The documents for the different IPs should be standardized
#31
jmaferreira
closed
5 years ago
10
General: All extra elements for SIP, AIP and DIP should be included in CSIP
#30
jmaferreira
closed
5 years ago
6
Proposal of adding Retention/Disposal elements
#29
jmaferreira
opened
5 years ago
8
What is the difference between SIP12 and SIP9 on page 32-33. A bit confusing with what is meant by creator. Is it the creator of the SIP or the creator of the original information? Please clearify
#28
jmaferreira
closed
5 years ago
4
The issue is repeated on page 19 in relation to the table describing fileSec (The following table describes the main differences in the fileSec between an EARK SIP and the CSIP.)
#27
jmaferreira
closed
5 years ago
2
Page 11 + Page 19: The sentence just before the table says: “The following table describes the main differences in the metsHdr between an EARK SIP and the CSIP.” The use of “main” is very confusing.
#26
jmaferreira
closed
5 years ago
1
The cardinality of METS element SIP12 assumes that there can only be one archival creator for a SIP (Cardinality 0..1)
#25
jmaferreira
closed
5 years ago
3
SIP32: "Follows the requirements in the CSIP profile", but CSIP does not say anything about this. Is this E-ARK specific attribute actually needed, since there is @MIMETYPE?
#24
jmaferreira
closed
4 years ago
7
Ch. 5.5 Appendix E: This whole appendix is unnecessary, since the document is not very large.
#23
jmaferreira
closed
5 years ago
1
Ch. 5.4 Appendix D: There are strings "###" that should be revised.
#22
jmaferreira
closed
4 years ago
6
Example in Page 17: CSIP agent requirement (software agent) is missing.
#21
jmaferreira
closed
5 years ago
5
Tables: "See also” in the end of some cells is not clear, for example where does "See also: Alternative records ID's” actually refer to?
#20
jmaferreira
closed
4 years ago
8
Tables: sometimes "metsHDR" element, as it should be "metsHdr".
#19
jmaferreira
closed
5 years ago
1
The are nulls in the auto-generated markdown
#18
hsilva-keep
closed
5 years ago
9
Mferreira v2.0.0
#17
jmaferreira
closed
5 years ago
0
Requirements table generator has a bug. The generated tables are broken due to spaces in the second line ("| -- | -- |")
#16
jmaferreira
closed
5 years ago
6
Typo in the METS profile: The req. ID "CSIP20" should be "SIP20"
#15
jmaferreira
closed
5 years ago
2
Creation of SIP Profile and vocabulary and extension schema
#14
karinbredenberg
closed
5 years ago
0
Mferreira v2.0.0
#13
jmaferreira
closed
5 years ago
0
Update/replace all the images with a common design (see CS IP)
#12
jmaferreira
closed
5 years ago
4
Review the entire document for typos
#11
jmaferreira
closed
5 years ago
3
Check all the examples against the profile
#10
jmaferreira
closed
5 years ago
1
Check if the links still work
#9
jmaferreira
closed
5 years ago
1
Make sure the SIP is compatible with the restrictions imposed by the CSIP
#8
jmaferreira
closed
5 years ago
1
Mention of content information type specifications
#7
PhillipTommerholt
closed
5 years ago
2
Have a way of specifying the order by which SIP should be ingested in order to support AIP updates via the ingest process
#6
jmaferreira
opened
5 years ago
4
Make sure that XML element included in the text are rendered properly in markdown.
#5
jmaferreira
closed
5 years ago
1
Make sure that all the footnotes have been converted properly to markdown
#4
jmaferreira
closed
5 years ago
1
Include missing tables on the markdown version
#3
jmaferreira
closed
5 years ago
1
I propose removing section "6 Summary"
#2
jmaferreira
closed
5 years ago
1
Please update the README.md to include more information about the purpose of this repository
#1
jmaferreira
closed
7 years ago
1
Previous