From 4f007f0172f0d60e34e7109763c4903769bceafd Mon Sep 17 00:00:00 2001
From: Juha Henriksson <105717772+juhahenriksson@users.noreply.github.com>
Date: Fri, 1 Dec 2023 07:58:45 +0200
Subject: [PATCH] Update RFC-0034.md
Added link to Europeana Digitization Handbook
---
files/releases/RFC-0034/RFC-0034.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/files/releases/RFC-0034/RFC-0034.md b/files/releases/RFC-0034/RFC-0034.md
index 1d75372..07cce36 100644
--- a/files/releases/RFC-0034/RFC-0034.md
+++ b/files/releases/RFC-0034/RFC-0034.md
@@ -23,6 +23,8 @@ Digitising audio recordings usually requires a lot of resources, as not all work
Signal retrieval from the original audio carriers is usually the most significant work step in terms of quality [^iasa1]. Preserving digitised and born-digital audio files requires regular transfers to a new storage medium and migrations to new file formats. These should be taken into account when the audio material is transferred from the original storage medium for the first time.
+A somewhat simpler audio digitisation workflow aimed at small and medium-sized cultural heritage organizations can be found in Europeana Digitization Handbook [^eur1].
+
# Selecting materials for digitisation
Digitising recordings is expensive and slow, and it takes a lot of human resources. If the audio collection to be digitized is extensive, choices must be made regarding what to digitise and in what order. In the selection and prioritisation of the material to be digitised, there are several different perspectives that should be taken into account.
@@ -126,6 +128,7 @@ The technical metadata should preferably contain, for example, the following inf
+[^eur1]:
[^iasa1]:
[^iasa2]:
[^iasa3]: