<?xml version="1.0" encoding="utf-8"?>
<mets:mets xmlns:mets="http://www.loc.gov/METS/">
  <mets:dmdSec ID="ie-dmd">
    <mets:mdWrap MDTYPE="DC">
      <mets:xmlData>
        <dc:record xmlns:dc="http://purl.org/dc/elements/1.1/">
          <dc:date>2023</dc:date>
          <dc:date>2023-05-31</dc:date>
          <dc:identifier type="doi">10.17192/bfdm.2023.3.8562</dc:identifier>
          <dc:identifier>urn:nbn:de:hebis:04-0008-2023-311-85622</dc:identifier>
          <dc:creator>keine Angabe</dc:creator>
          <dc:title>Das Forschungsdatenzentrum der Universität Hamburg</dc:title>
          <dcterms:license xmlns:dcterms="http://purl.org/dc/terms/">http://creativecommons.org/licenses/by/4.0</dcterms:license>
          <dcterms:accessRights xmlns:dcterms="http://purl.org/dc/terms/">public -Frei abrufbar</dcterms:accessRights>
          <dc:description>The more recent discussion of research data practices at relevant conferences, workshops and respective publications suggest substantially different foci of problems and solutions in managing data between scientific disciplines. There seems to be a particularly profound gap in natural science and humanities whereas social and life sciences are placed somewhere in between. Indeed data centers tailored to the specific needs of a single discipline (physics, chemistry, climate studies) are numerous in science and tend to be nearly absent for a specific humanities subject. While the former ask for and report solutions on scaling up (larger quantities of data can be run by the same application) and scaling out (larger quantities of data can use the same infrastructure), the latter are concerned with the heterogeneity of relatively small amounts of data (long-tail problem) and a divergence of agreed standards; something we may term as cross scaling. In either case, an efficiency problem has to be solved. On the one hand, huge amounts of data have to be handled within an acceptable time frame, on the other hand, many different applications with diverse functionalities have to be handled with an acceptable number of resources.+nbsp;
We would like to argue here that independent from the discipline either optimization problem should be addressed. Throughout the last decade, we have also observed that projects in science diversify and prefer individualized solutions which additionally hints at increasing data heterogeneity in natural science as well while, at the same time, some humanities projects produce petabytes of data. To show the necessity of a differentiated approach, the research data center of Universität Hamburg is offered as a case in point. The evolution of the center specialized in humanities projects to a research data center offering services for the whole university whereas other disciplinary data centers continue to exist side by side illustrates the entire range of tasks of data stewardship. It includes the continuous development of services while getting more and more involved in natural science projects as well as task sharing and communication with other data institutions. A core asset to understand the requirements of each discipline is a multidisciplinary team. Yet, the main organizing principle of the offered services centers around the stages of the data life cycle (1. data creation and deposit, 2. managing active data, 3. data repositories and archives, 4. data catalog and registries). The interdigitation of these stages is paramount in the long term strategy.</dc:description>
          <dc:subject>Open Access</dc:subject>
          <dc:subject>Data Literacy</dc:subject>
          <dc:subject>Forschungsdatenlebenszyklus</dc:subject>
          <dc:subject>Forschungsrepositorium</dc:subject>
          <dc:subject>Forschungsinformation</dc:subject>
        </dc:record>
      </mets:xmlData>
    </mets:mdWrap>
  </mets:dmdSec>
  <mets:amdSec ID="ie-amd">
    <mets:techMD ID="ie-amd-tech">
      <mets:mdWrap MDTYPE="OTHER" OTHERMDTYPE="dnx">
        <mets:xmlData>
          <dnx xmlns="http://www.exlibrisgroup.com/dps/dnx">
            <section id="generalIECharacteristics">
              <record>
                <key id="IEEntityType">JournalArticle</key>
              </record>
            </section>
          </dnx>
        </mets:xmlData>
      </mets:mdWrap>
    </mets:techMD>
    <mets:rightsMD ID="ie-amd-rights">
      <mets:mdWrap MDTYPE="OTHER" OTHERMDTYPE="dnx">
        <mets:xmlData>
          <dnx xmlns="http://www.exlibrisgroup.com/dps/dnx">
            <section id="accessRightsPolicy">
              <record>
                <key id="policyId">3</key>
                <key id="policyParameters"/>
                <key id="policyDescription">No restrictions</key>
              </record>
            </section>
          </dnx>
        </mets:xmlData>
      </mets:mdWrap>
    </mets:rightsMD>
    <mets:sourceMD ID="ie-amd-source-RDF">
      <mets:mdWrap MDTYPE="OTHER" OTHERMDTYPE="RDF">
        <mets:xmlData>
          <rdf:RDF xmlns:aiiso="http://purl.org/vocab/aiiso/schema#" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:dctypes="http://purl.org/dc/dcmitype/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sco="http://schema.org/" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:void="http://rdfs.org/ns/void#">
<dcterms:BibliographicResource rdf:about="https://journals.uni-marburg.de/0008/2023/311/8562"><dcterms:identifier>https://doi.org/10.17192/bfdm.2023.3.8562</dcterms:identifier>
<dcterms:source rdf:resource="https://bausteine-fdm.de/article/view/8562"/>
<dcterms:isPartOf><dcterms:BibliographicResource rdf:about="https://journals.uni-marburg.de/0008/2023/311"><dcterms:alternative>Beiträge aus dem Workshop "Data Stewardship goes Germany" der FDM-AG der TU9-Allianz</dcterms:alternative>
<dcterms:created>2023</dcterms:created>
<dcterms:identifier>urn:nbn:de:hebis:04-0008-2023-3110</dcterms:identifier>
<dcterms:title>2023, 3</dcterms:title>
<dcterms:isPartOf><dcterms:BibliographicResource rdf:about="https://journals.uni-marburg.de/0008"><sco:issn>2626-7489</sco:issn>
<sco:leiCode>2947344-5</sco:leiCode>
<dcterms:source rdf:resource="https://bausteine-fdm.de"/>
<foaf:img>https://journals.uni-marburg.de/0008/cover.png</foaf:img>
<dcterms:type rdf:resource="http://purl.org/spar/fabio/Journal"/>
<dcterms:subject><skos:Concept rdf:about="http://dewey.info/class/000"><skos:prefLabel xml:lang="de">Forschungsdatenmanagement</skos:prefLabel>
<skos:prefLabel xml:lang="en">Research Data Management</skos:prefLabel>
</skos:Concept>
</dcterms:subject>
<dcterms:contributor><aiiso:Center rdf:about="http://www.forschungsdaten.org"><foaf:name>AG Forschungsdaten</foaf:name>
</aiiso:Center>
</dcterms:contributor>
<dcterms:identifier>urn:nbn:de:hebis:04-00084</dcterms:identifier>
<dcterms:title>Bausteine Forschungsdatenmanagement</dcterms:title>
<sco:additionalType>Periodical</sco:additionalType>
<dcterms:publisher><foaf:Organization rdf:about="https://d-nb.info/gnd/4241352-7/about/lds.rd"><foaf:address>Deutschhausstraße 9, 35037 Marburg</foaf:address>
<foaf:based_near>Marburg</foaf:based_near>
<foaf:name>Philipps-Universität Marburg</foaf:name>
</foaf:Organization>
</dcterms:publisher>
</dcterms:BibliographicResource>
</dcterms:isPartOf>
<dcterms:source rdf:resource="https://bausteine-fdm.de/issue/view/311"/>
<dcterms:type rdf:resource="http://purl.org/spar/fabio/JournalIssue"/>
<sco:issueNumber>3</sco:issueNumber>
<foaf:img>https://journals.uni-marburg.de/0008/2023/311/cover.png</foaf:img>
<dcterms:license rdf:resource="https://creativecommons.org/licenses/by/4.0/"/>
<sco:additionalType>PeriodicalPart</sco:additionalType>
<dcterms:issued>2023-07-14</dcterms:issued>
</dcterms:BibliographicResource>
</dcterms:isPartOf>
<dcterms:creator><rdf:Seq><rdf:li><foaf:Person><foaf:givenName>Hagen</foaf:givenName>
<foaf:familyName>Peukert</foaf:familyName>
<foaf:name>Peukert, Hagen</foaf:name>
</foaf:Person>
</rdf:li>
<rdf:li><foaf:Person><foaf:givenName>Sylvia</foaf:givenName>
<foaf:familyName>Melzer</foaf:familyName>
<foaf:name>Melzer, Sylvia</foaf:name>
</foaf:Person>
</rdf:li>
<rdf:li><foaf:Person><foaf:givenName>Juliane</foaf:givenName>
<foaf:familyName>Jacob</foaf:familyName>
<foaf:name>Jacob, Juliane</foaf:name>
</foaf:Person>
</rdf:li>
<rdf:li><foaf:Person><foaf:givenName>Iris</foaf:givenName>
<foaf:familyName>Vogel</foaf:familyName>
<foaf:name>Vogel, Iris</foaf:name>
</foaf:Person>
</rdf:li>
<rdf:li><foaf:Person><foaf:givenName>Kai</foaf:givenName>
<foaf:familyName>Wörner</foaf:familyName>
<foaf:name>Wörner, Kai</foaf:name>
</foaf:Person>
</rdf:li>
<rdf:li><foaf:Person><foaf:givenName>Steffen</foaf:givenName>
<foaf:familyName>Grünler</foaf:familyName>
<foaf:name>Grünler, Steffen</foaf:name>
</foaf:Person>
</rdf:li>
<rdf:li><foaf:Person><foaf:givenName>Lisa</foaf:givenName>
<foaf:familyName>Brase</foaf:familyName>
<foaf:name>Brase, Lisa</foaf:name>
</foaf:Person>
</rdf:li>
<rdf:li><foaf:Person><foaf:givenName>Alexander</foaf:givenName>
<foaf:familyName>Heinrich</foaf:familyName>
<foaf:name>Heinrich, Alexander</foaf:name>
</foaf:Person>
</rdf:li>
<rdf:li><foaf:Person><foaf:givenName>Stefan</foaf:givenName>
<foaf:familyName>Thiemann</foaf:familyName>
<foaf:name>Thiemann, Stefan</foaf:name>
</foaf:Person>
</rdf:li>
</rdf:Seq>
</dcterms:creator>
<dcterms:subject><skos:Concept><rdfs:label>Open Access</rdfs:label>
</skos:Concept>
</dcterms:subject>
<dcterms:issued>2023-05-31</dcterms:issued>
<dcterms:subject><skos:Concept><rdfs:label>Data Literacy</rdfs:label>
</skos:Concept>
</dcterms:subject>
<dcterms:created>2023</dcterms:created>
<dcterms:abstract>The more recent discussion of research data practices at relevant conferences, workshops and respective publications suggest substantially different foci of problems and solutions in managing data between scientific disciplines. There seems to be a particularly profound gap in natural science and humanities whereas social and life sciences are placed somewhere in between. Indeed data centers tailored to the specific needs of a single discipline (physics, chemistry, climate studies) are numerous in science and tend to be nearly absent for a specific humanities subject. While the former ask for and report solutions on scaling up (larger quantities of data can be run by the same application) and scaling out (larger quantities of data can use the same infrastructure), the latter are concerned with the heterogeneity of relatively small amounts of data (long-tail problem) and a divergence of agreed standards; something we may term as cross scaling. In either case, an efficiency problem has to be solved. On the one hand, huge amounts of data have to be handled within an acceptable time frame, on the other hand, many different applications with diverse functionalities have to be handled with an acceptable number of resources.+nbsp;
We would like to argue here that independent from the discipline either optimization problem should be addressed. Throughout the last decade, we have also observed that projects in science diversify and prefer individualized solutions which additionally hints at increasing data heterogeneity in natural science as well while, at the same time, some humanities projects produce petabytes of data. To show the necessity of a differentiated approach, the research data center of Universität Hamburg is offered as a case in point. The evolution of the center specialized in humanities projects to a research data center offering services for the whole university whereas other disciplinary data centers continue to exist side by side illustrates the entire range of tasks of data stewardship. It includes the continuous development of services while getting more and more involved in natural science projects as well as task sharing and communication with other data institutions. A core asset to understand the requirements of each discipline is a multidisciplinary team. Yet, the main organizing principle of the offered services centers around the stages of the data life cycle (1. data creation and deposit, 2. managing active data, 3. data repositories and archives, 4. data catalog and registries). The interdigitation of these stages is paramount in the long term strategy.</dcterms:abstract>
<dcterms:subject><skos:Concept><rdfs:label>Forschungsdatenlebenszyklus</rdfs:label>
</skos:Concept>
</dcterms:subject>
<dcterms:language><dcterms:LinguisticSystem rdf:about="http://id.loc.gov/vocabulary/iso639-2/ger"><dcterms:hasVersion rdf:resource="http://id.loc.gov/vocabulary/iso639-1/de"/>
<rdf:value xml:lang="en">German</rdf:value>
</dcterms:LinguisticSystem>
</dcterms:language>
<dcterms:type rdf:resource="http://purl.org/spar/fabio/JournalArticle"/>
<sco:additionalType>article</sco:additionalType>
<dcterms:alternative>Auf dem Weg zu einem gemeinsamen Verständnis im Umgang mit Forschungsdaten in den Natur-, Sozial- und Geisteswissenschaften</dcterms:alternative>
<dcterms:license rdf:resource="http://creativecommons.org/licenses/by/4.0"/>
<dcterms:mediator><dcterms:Agent rdf:about="http://archiv.ub.uni-marburg.de"><rdfs:label>Universitätsbibliothek Marburg</rdfs:label>
<foaf:name>Publikationsserver der Universitätsbibliothek Marburg</foaf:name>
</dcterms:Agent>
</dcterms:mediator>
<foaf:img>https://journals.uni-marburg.de/0008/2023/311/8562/8562.png</foaf:img>
<dcterms:title xml:lang="de">Das Forschungsdatenzentrum der Universität Hamburg</dcterms:title>
<dcterms:hasPart><dctypes:Text rdf:about="https://bausteine-fdm.de/article/download/8562/8289"><dcterms:issued>2023-05-31</dcterms:issued>
<dcterms:source rdf:resource="https://bausteine-fdm.de/article/download/8562/8289"/>
<dcterms:format><dcterms:MediaTypeOrExtent><rdfs:label>application/pdf</rdfs:label>
</dcterms:MediaTypeOrExtent>
</dcterms:format>
</dctypes:Text>
</dcterms:hasPart>
<dcterms:subject><skos:Concept><rdfs:label>Forschungsrepositorium</rdfs:label>
</skos:Concept>
</dcterms:subject>
<dcterms:identifier>urn:nbn:de:hebis:04-0008-2023-311-85622</dcterms:identifier>
<dcterms:modified>2024-01-09</dcterms:modified>
<dcterms:subject><skos:Concept><rdfs:label>Forschungsinformation</rdfs:label>
</skos:Concept>
</dcterms:subject>
</dcterms:BibliographicResource></rdf:RDF>
        </mets:xmlData>
      </mets:mdWrap>
    </mets:sourceMD>
  </mets:amdSec>
  <mets:amdSec ID="rep1-amd">
    <mets:techMD ID="rep1-amd-tech">
      <mets:mdWrap MDTYPE="OTHER" OTHERMDTYPE="dnx">
        <mets:xmlData>
          <dnx xmlns="http://www.exlibrisgroup.com/dps/dnx">
            <section id="generalRepCharacteristics">
              <record>
                <key id="preservationType">PRESERVATION_MASTER</key>
                <key id="usageType">VIEW</key>
                <key id="representationEntityType">PDF</key>
                <key id="label">PRESERVATION_MASTER</key>
              </record>
            </section>
          </dnx>
        </mets:xmlData>
      </mets:mdWrap>
    </mets:techMD>
  </mets:amdSec>
  <mets:amdSec ID="fid1-1-amd">
    <mets:techMD ID="fid1-1-amd-tech">
      <mets:mdWrap MDTYPE="OTHER" OTHERMDTYPE="dnx">
        <mets:xmlData>
          <dnx xmlns="http://www.exlibrisgroup.com/dps/dnx">
            <section id="generalFileCharacteristics">
              <record>
                <key id="fileMIMEType">application/pdf</key>
                <key id="label">8289</key>
                <key id="fileOriginalPath">//bausteine-fdm.de/article/download/8562/8289</key>
                <key id="fileOriginalName">8289</key>
                <key id="fileSizeBytes"/>
              </record>
            </section>
            <section id="fileFixity">
              <record>
                <key id="fixityType">MD5</key>
                <key id="fixityValue"/>
              </record>
            </section>
          </dnx>
        </mets:xmlData>
      </mets:mdWrap>
    </mets:techMD>
    <mets:rightsMD ID="fid1-1-amd-rights">
      <mets:mdWrap MDTYPE="OTHER" OTHERMDTYPE="dnx">
        <mets:xmlData>
          <dnx xmlns="http://www.exlibrisgroup.com/dps/dnx"/>
        </mets:xmlData>
      </mets:mdWrap>
    </mets:rightsMD>
    <mets:digiprovMD ID="fid1-1-amd-digiprov">
      <mets:mdWrap MDTYPE="OTHER" OTHERMDTYPE="dnx">
        <mets:xmlData>
          <dnx xmlns="http://www.exlibrisgroup.com/dps/dnx"/>
        </mets:xmlData>
      </mets:mdWrap>
    </mets:digiprovMD>
  </mets:amdSec>
  <mets:fileSec>
    <mets:fileGrp ADMID="rep1-amd" ID="rep1" USE="View">
      <mets:file ID="fid1-1" ADMID="fid1-1-amd" MIMETYPE="application/pdf">
        <mets:FLocat xmlns:xlin="http://www.w3.org/1999/xlink" LOCTYPE="URL" xlin:href="https://bausteine-fdm.de/article/download/8562/8289"/>
      </mets:file>
    </mets:fileGrp>
  </mets:fileSec>
  <mets:structMap ID="struct-1" TYPE="PHYSICAL">
    <mets:div LABEL="PRESERVATION_MASTER">
      <mets:div ID="phys_pdf_1" ORDER="1" TYPE="FILE">
        <mets:fptr FILEID="fid1-1"/>
      </mets:div>
    </mets:div>
  </mets:structMap>
</mets:mets>
