Lippe brickmakers: archival pages transcriptions
https://datasets.iisg.amsterdam/dataset.xhtml?persistentId=hdl:10622/1RNBFT
Title: Lippe brickmakers project: archival pages transcriptions
identifier: lippe_page_scans
This dataset is part of the Lippe brickmakers project.
It contains two files.
A file in tabular format (.tab): in each row there is metadata and (if done by the researchers) a transcription of one digitized page from the Lippische Ziegler archive.
A file in n-triples format (.nt), wich contains the same data as the previous file but represented in linked data format (triples). This linked data version is the basis for exploring and querying the data via this "data story" via the linked data publication platform.
The images below show how the data is structured:
1. General structure:
2. Specific data for one page:
These are the columns in this dataset and what they contain:
file_Id: the id of the digital scan file.
signatur: or reference number. It is a code used by archives to mark and identify one element within the archival finding aid (also called "inventaris"). It could be considered as an equivalent of a "chapter" in the finding aid. Example from the Lippe archive: there is a "fond" (broader unit) identified with number L77A. This fond contains different "signaturen", for example, "4698", or "4716". Both numbers (L77A, and 4698) were assigned by the archive who hosted the original scans (Landesarchiv Nordrhein-Westfalen).
inventory_number: This is the same as the "signatur" but it's the sequential number that was given to the item by the IISH archive. At the IISH, the Fonds got also a different identification number (ARCH03497). Thus, ARCH03497.1 means that the Lippe archive got the fonds number ARCH03497, and the .1 is referring to the first item in the finding aid.
folio: same as "page", it contains the specific number of a page in the inventory item; e.g., 260r indicates that the page is 260 in the reverse of the page. (v = front of the page, "vorderseite"; r = reverse side of the page).
page_number_cv: Because the digital pages are displayed using the IIIF protocols and viewers, we use this column to register the page number in the "IIIF universal viewer". For example, for the first inventory number, this is the scans' IIIF viewer: https://access.iisg.amsterdam/universalviewer/#?manifest=https://hdl.handle.net/10622/ARCH03497.1?locatt=view:manifest. There, one can see a page navigation feature on the top, where the page number is displayed. This page number is given by the canvas viewer (cv) only, and it differs from the (hand-written) folio page number, and it's also different from the page number that is stored digitally (see "page_number_manifest").
page_number_access: the page number stored in the IIIF manifest (a kind of page number of the digital stored scan).
page_access_url: this is the "url" that points to a specific location of one page in the IIIF manifest.
transcription: some pages contain the transcriptions done by the main researchers. Here the transcription is entered as textual content.
More information about the Lippe brick-makers project ("Lippische Ziegler" project can be found in the Lippe brickmakers project dataverse. The linked data version can be used for exploring and querying the data in this "data story" via the linked data publication platform.
hasPart
Lippe brickmakers: archival pages transcriptions
https://datasets.iisg.amsterdam/dataset.xhtml?persistentId=hdl:10622/1RNBFT
Title: Lippe brickmakers project: archival pages transcriptions
identifier: lippe_page_scans
This dataset is part of the Lippe brickmakers project.
It contains two files.
A file in tabular format (.tab): in each row there is metadata and (if done by the researchers) a transcription of one digitized page from the Lippische Ziegler archive.
A file in n-triples format (.nt), wich contains the same data as the previous file but represented in linked data format (triples). This linked data version is the basis for exploring and querying the data via this "data story" via the linked data publication platform.
The images below show how the data is structured:
1. General structure:
2. Specific data for one page:
These are the columns in this dataset and what they contain:
file_Id: the id of the digital scan file.
signatur: or reference number. It is a code used by archives to mark and identify one element within the archival finding aid (also called "inventaris"). It could be considered as an equivalent of a "chapter" in the finding aid. Example from the Lippe archive: there is a "fond" (broader unit) identified with number L77A. This fond contains different "signaturen", for example, "4698", or "4716". Both numbers (L77A, and 4698) were assigned by the archive who hosted the original scans (Landesarchiv Nordrhein-Westfalen).
inventory_number: This is the same as the "signatur" but it's the sequential number that was given to the item by the IISH archive. At the IISH, the Fonds got also a different identification number (ARCH03497). Thus, ARCH03497.1 means that the Lippe archive got the fonds number ARCH03497, and the .1 is referring to the first item in the finding aid.
folio: same as "page", it contains the specific number of a page in the inventory item; e.g., 260r indicates that the page is 260 in the reverse of the page. (v = front of the page, "vorderseite"; r = reverse side of the page).
page_number_cv: Because the digital pages are displayed using the IIIF protocols and viewers, we use this column to register the page number in the "IIIF universal viewer". For example, for the first inventory number, this is the scans' IIIF viewer: https://access.iisg.amsterdam/universalviewer/#?manifest=https://hdl.handle.net/10622/ARCH03497.1?locatt=view:manifest. There, one can see a page navigation feature on the top, where the page number is displayed. This page number is given by the canvas viewer (cv) only, and it differs from the (hand-written) folio page number, and it's also different from the page number that is stored digitally (see "page_number_manifest").
page_number_access: the page number stored in the IIIF manifest (a kind of page number of the digital stored scan).
page_access_url: this is the "url" that points to a specific location of one page in the IIIF manifest.
transcription: some pages contain the transcriptions done by the main researchers. Here the transcription is entered as textual content.
More information about the Lippe brick-makers project ("Lippische Ziegler" project can be found in the Lippe brickmakers project dataverse. The linked data version can be used for exploring and querying the data in this "data story" via the linked data publication platform.
subtitle
Page transcriptions and links to the original archival scans
type
accessRequestRequired
publicationCitation
Joergens, B. & J. Lucassen (ed ...... /orcid.org/0009-0009-6065-3947
about
Arts and Humanities
addressCountry
contactPoints
dateCreated
2024-04-02T12:42:36Z
dateModified
2024-04-08T12:38:34Z
datePublished
2024-04-08T12:38:34Z
description
https://datasets.iisg.amsterdam/dataset.xhtml?persistentId=hdl:10622/1RNBFT
Title: Lippe brickmakers project: archival pages transcriptions
identifier: lippe_page_scans
This dataset is part of the Lippe brickmakers project.
It contains two files.
The images below show how the data is structured:
1. General structure:
2. Specific data for one page:
These are the columns in this dataset and what they contain:
file_Id: the id of the digital scan file.
signatur: or reference number. It is a code used by archives to mark and identify one element within the archival finding aid (also called "inventaris"). It could be considered as an equivalent of a "chapter" in the finding aid. Example from the Lippe archive: there is a "fond" (broader unit) identified with number L77A. This fond contains different "signaturen", for example, "4698", or "4716". Both numbers (L77A, and 4698) were assigned by the archive who hosted the original scans (Landesarchiv Nordrhein-Westfalen).
inventory_number: This is the same as the "signatur" but it's the sequential number that was given to the item by the IISH archive. At the IISH, the Fonds got also a different identification number (ARCH03497). Thus, ARCH03497.1 means that the Lippe archive got the fonds number ARCH03497, and the .1 is referring to the first item in the finding aid.
folio: same as "page", it contains the specific number of a page in the inventory item; e.g., 260r indicates that the page is 260 in the reverse of the page. (v = front of the page, "vorderseite"; r = reverse side of the page).
page_number_cv: Because the digital pages are displayed using the IIIF protocols and viewers, we use this column to register the page number in the "IIIF universal viewer". For example, for the first inventory number, this is the scans' IIIF viewer: https://access.iisg.amsterdam/universalviewer/#?manifest=https://hdl.handle.net/10622/ARCH03497.1?locatt=view:manifest. There, one can see a page navigation feature on the top, where the page number is displayed. This page number is given by the canvas viewer (cv) only, and it differs from the (hand-written) folio page number, and it's also different from the page number that is stored digitally (see "page_number_manifest").
page_number_access: the page number stored in the IIIF manifest (a kind of page number of the digital stored scan).
page_access_url: this is the "url" that points to a specific location of one page in the IIIF manifest.
transcription: some pages contain the transcriptions done by the main researchers. Here the transcription is entered as textual content.
More information about the Lippe brick-makers project ("Lippische Ziegler" project can be found in the Lippe brickmakers project dataverse. The linked data version can be used for exploring and querying the data in this "data story" via the linked data publication platform.
It contains two files.
- A file in tabular format (.tab): in each row there is metadata and (if done by the researchers) a transcription of one digitized page from the Lippische Ziegler archive.
- A file in n-triples format (.nt), wich contains the same data as the previous file but represented in linked data format (triples). This linked data version is the basis for exploring and querying the data via this "data story" via the linked data publication platform.
The images below show how the data is structured:
1. General structure:
2. Specific data for one page:
These are the columns in this dataset and what they contain:
More information about the Lippe brick-makers project ("Lippische Ziegler" project can be found in the Lippe brickmakers project dataverse. The linked data version can be used for exploring and querying the data in this "data story" via the linked data publication platform.
distribution
geoWithin
POLYGON((3.3708631707774 53.46 ...... 708631707774 53.465827133613))
POLYGON((5.86500017310021 55.0 ...... 00017310021 55.0565271350945))
hasPart
identifier
inLanguage
keywords
license
name
Lippe brickmakers: archival pages transcriptions
uploadDate
2020-02-03