<div dir="ltr"><div>Hi Noemi,</div><div>This is an area where there has been a lot of interest both in capturing the process information (sometimes referred to as paradata) around data capture and also in the specific processing activities. As you note there is not a specific section covering interview transcription as we have not fully addressed qualitative data of which interview content is a part. However, I think the appropriate approach with the DDI Lifecycle as its stands now is to use the ProcessingEvent giving it a name, label and description and then use ProcessingInstruction (generation or general instruction as appropriate) to provide the specific rules and steps. Each of these allows the use of the control constructs (with GenerationInstruction) if you need to order or specify conditions for specific instructions. You can also provide a reference to quality statements (established practices or guidelines followed) within the ProcessingEvent.</div><div><br></div><div>Others may have additional thoughts on this.</div><div>Wendy<br></div></div><br><div class="gmail_quote"><div class="gmail_attr" dir="ltr">On Wed, Jul 3, 2019 at 8:15 AM Noemi Betancort <<a href="mailto:noemi.betancort@suub.uni-bremen.de">noemi.betancort@suub.uni-bremen.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<div bgcolor="#FFFFFF">
<p>Dear DDI users! <br>
</p>
<p>I have a question about the documentation of the process of
interview transcribing: I want to document which transcription
methodology was used for the described data, maybe the person who
made the transcription and eventually the tool or software used.</p>
<p>I would like to include it in the data collection module ("a
maintainable module containing information on activities related
to data collection/capture and the <b>processing required for the
creation a data product</b>") as it is normally a processing
event. <br>
</p>
<p>However in the element ProcessingEvent I can't find a suitable
element for that. I might expect a more generic child-element like
TypeOfProcessingEvent, which allows you to document other
processing events in addition to those (cleaning operation,
control operation...) already offered.<br>
</p>
<p>At
<a class="gmail-m_8602172058024357346moz-txt-link-freetext" href="http://www.ddialliance.org/Specification/DDI-CV/LifecycleEventType_1.0.html" target="_blank">http://www.ddialliance.org/Specification/DDI-CV/LifecycleEventType_1.0.html</a>
we find the value DataProcessing.InterviewTranscriptions, so that
this kind of process is rather included in the archive module (as
transcribing may also ocurr at another point of time and not
within data collection/processing)</p>
<p>I wonder, how do you manage that? is the process of transcribing
actually relevant in your metadata?<br>
</p>
<p>Kind regards,</p>
<p>Noemi<br>
</p>
<pre class="gmail-m_8602172058024357346moz-signature" cols="72">--
Noemi Betancort Cabrera
Systems librarian and metadatamanager by Qualiservice
Dezernat Digitale Dienste
Staats- und Universitätsbibliothek Bremen
Bibliothekstraße 9
Bremen - Germany
Tel. +49 (0)421/218-59592
Fax. +49 (0)421/218-98 59592</pre>
</div>
_______________________________________________<br>
DDI-users mailing list<br>
<a href="mailto:DDI-users@icpsr.umich.edu" target="_blank">DDI-users@icpsr.umich.edu</a><br>
<a href="http://lists.icpsr.umich.edu/mailman/listinfo/ddi-users" target="_blank" rel="noreferrer">http://lists.icpsr.umich.edu/mailman/listinfo/ddi-users</a><br>
</blockquote></div><br clear="all"><br>-- <br><div class="gmail_signature" dir="ltr"><div>Wendy L. Thomas Phone: +1 612.624.4389</div><div>Data Access Core Director Fax: +1 612.626.8375</div><div>Minnesota Population Center Email: <a href="mailto:wlt@umn.edu" target="_blank">wlt@umn.edu</a></div><div>University of Minnesota</div><div>50 Willey Hall</div><div>225 19th Avenue South</div><div>Minneapolis, MN 55455</div></div>