Changes for page Infrastructure, Services & Tools

Last modified by Veronika Kocher on Friday, 04 Sep 2026 14:45

Manage
- Copy
Actions
- Export
- Print Preview
Viewers

From 2.6 to 2.7 From 6.2 to 6.3

From version 2.7

edited by Veronika Kocher
on Friday, 28 Aug 2026 15:46

Change comment: There is no comment for this version

To version 6.2

edited by Veronika Kocher
on Friday, 04 Sep 2026 14:23

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Default language

...	...	@@ -1,0 +1,1 @@
	1	+en

tags

...	...	@@ -1,0 +1,1 @@
	1	+art and research\|enable\|infrastructure\|services\|tools\|institutional services\|software\|repositories\|research infrastructure\|it services\|digital tools\|infrastruktur\|dienste\|werkzeuge

Content

@@ -1,47 +1,256 @@
--Identify institutional infrastructure, services and tools that can support storage, collaboration, documentation and publication.
++{{html clean="false"}}
--== Overview ==
++<style>
++.ist{max-width:1400px;margin:0 auto;color:#322f2b}
++.ist *{box-sizing:border-box}
++.ist-card{border:1px solid #e3ded6;border-radius:11px;background:#fcfbf8;box-shadow:0 1px 3px rgba(0,0,0,.035)}
++.ist-hero{height:132px;overflow:hidden;background:#f1eee9;border-radius:11px 11px 0 0}
++.ist-hero img{width:100%;height:100%;object-fit:cover;object-position:center 45%;display:block}
++.ist-eye{font-size:12px;font-weight:700;letter-spacing:.075em;text-transform:uppercase}
++.ist-sec{margin:0 0 27px 0}
++.ist-sec h3{font-size:22px;line-height:1.25;margin:0 0 7px;color:#35312d;text-align:left!important;text-align-last:left!important;text-justify:auto!important;word-spacing:normal!important}
++.ist-sec>p{color:#625d56;line-height:1.58;margin:0 0 13px}
++.ist-grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(285px,1fr));gap:12px}
++.ist-grid-2{display:grid;grid-template-columns:repeat(2,minmax(300px,1fr));gap:12px}
++.ist-info{padding:15px 17px;border:1px solid #c7e5ed;border-left:5px solid #21b6d7;background:#eaf6f9;border-radius:8px;color:#365e68;line-height:1.5}
++.ist-info strong{color:#2d5661}
++.ist-infra{padding:15px 17px;border:1px solid #cfe8d6;border-left:5px solid #38b76a;background:#edf9f1;border-radius:8px;color:#3f6d4b;line-height:1.5}
++.ist-infra strong{color:#355f42}
++.ist-warn{padding:15px 17px;border:1px solid #efd9cc;border-left:5px solid #e94b13;background:#fff6f1;border-radius:8px;color:#67564e;line-height:1.5}
++.ist-warn strong{color:#744531}
++.ist-check{position:relative;padding:12px 13px 12px 37px;border:1px solid #e3ded6;border-radius:8px;background:#fffdf9;color:#504a44;line-height:1.5}
++.ist-check:before{content:"✓";position:absolute;left:13px;top:10px;color:#38b76a;font-weight:800}
++.ist-step{position:relative;padding:13px 14px 13px 50px;border:1px solid #e3ded6;border-radius:8px;background:#fcfbf8;min-height:76px}
++.ist-step .n{position:absolute;left:13px;top:13px;width:26px;height:26px;border-radius:50%;display:flex;align-items:center;justify-content:center;background:#e6f3e9;color:#3f6d4b;font-weight:800;font-size:12px}
++.ist-step h4{margin:0 0 4px;font-size:16px;line-height:1.3;color:#3b352e;text-align:left!important;text-align-last:left!important;text-justify:auto!important;word-spacing:normal!important}
++.ist-step p{margin:0;color:#625d56;line-height:1.45}
++.ist-scenario{padding:14px 15px;border:1px solid #e3ded6;border-top:4px solid #38b76a;border-radius:9px;background:#fcfbf8}
++.ist-scenario h4{margin:0 0 6px;font-size:16px;color:#3e372e;text-align:left!important;word-spacing:normal!important}
++.ist-scenario p{margin:0;color:#625d56;line-height:1.5}
++.ist-table-wrap{overflow-x:auto;border:1px solid #e3ded6;border-radius:8px}
++.ist-table{width:100%;border-collapse:collapse;background:#fffdf9;min-width:980px}
++.ist-table th,.ist-table td{padding:10px 11px;border-bottom:1px solid #e3ded6;vertical-align:top;text-align:left;line-height:1.4}
++.ist-table th{background:#f3efe8;color:#403b36;font-weight:700}
++.ist-table tr:last-child td{border-bottom:0}
++.ist-service-grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(260px,1fr));gap:10px}
++.ist-service{display:block;padding:13px 14px;border:1px solid #e3ded6;border-left:4px solid #38b76a;border-radius:8px;background:#fcfbf8;color:#2f2b27}
++.ist-service strong{display:block;margin-bottom:4px}
++.ist-service span{display:block;color:#625d56;line-height:1.45;font-weight:400}
++.ist-linkgrid{display:grid;grid-template-columns:repeat(auto-fit,minmax(260px,1fr));gap:8px}
++.ist-navlink{display:block;padding:10px 11px;border:1px solid #e9e4dc;border-left:3px solid #38b76a;border-radius:6px;background:#fffdf9;color:#252321;text-decoration:none;font-weight:600;line-height:1.35}
++.ist-navlink:hover,.ist-navlink:focus{background:#f6fbf7;text-decoration:none}
++.ist-resource-grid{display:grid;grid-template-columns:repeat(3,minmax(0,1fr));gap:12px}
++.ist-resource{padding:15px 16px;background:#fcfbf8;border:1px solid #e3ded6;border-radius:9px}
++.ist-resource strong{display:block;color:#4c4130;margin-bottom:4px}
++.ist-badge{display:inline-block;margin:5px 0 7px;padding:4px 8px;border-radius:14px;background:#fff4ee;border:1px solid #efd9cc;color:#8a4d36;font-size:11px;font-weight:700;letter-spacing:.055em;line-height:1.2}
++.ist h1,.ist h2,.ist h3,.ist h4,.ist h5,.ist h6,.ist h1 a,.ist h2 a,.ist h3 a,.ist h4 a,.ist h5 a,.ist h6 a{text-align:left!important;text-align-last:left!important;text-justify:auto!important;word-spacing:normal!important}
++@media(max-width:850px){.ist-grid-2,.ist-resource-grid{grid-template-columns:1fr}}
++@media(max-width:680px){.ist-hero{height:105px}.ist-sec h3{font-size:20px}}
++</style>
--Add a concise explanation of this topic and why it matters for Art & Research projects.
++<div class="ist">
--== What you need to know ==
++<section class="ist-card" style="margin-bottom:18px;overflow:hidden;border-left:6px solid #38b76a;">
++  <div class="ist-hero">
++    <img src="https://xwiki.uni-ak.ac.at/bin/download/Service%20Navigator/Art%20%26%20Research%20Services%20Navigator/WebHome/enable.png" alt="Infrastructure, services and tools for artistic and research projects" />
++  </div>
++  <div style="padding:18px 21px 20px;">
++    <div class="ist-eye" style="color:#3f6d4b;margin-bottom:5px;">PREPARE · SET UP INFRASTRUCTURE</div>
++    <h2 style="font-size:27px;line-height:1.2;margin:0 0 8px;color:#2c2926;">Choose infrastructure, services and tools according to the project's actual needs — and make dependencies visible early</h2>
++    <p style="margin:0;color:#5e5953;line-height:1.6;max-width:1160px;">
++      Digital systems, rooms, equipment, labs and specialist services can be essential project dependencies.
++      First check which institutional solutions already exist, what your project genuinely requires,
++      and how access, support, costs, data protection, export and handover will be organised.
++    </p>
++  </div>
++</section>
--* Key concepts
--* Relevant requirements
--* Important distinctions
++<div class="ist-info" style="margin-bottom:14px;">
++  <strong>Start from the task — not the tool.</strong>
++  Describe what the project needs to do first: store, collaborate, produce, document,
++  analyse, present, publish or hand over for the long term. Only then choose a specific system.
++</div>
--== What you need to do ==
++<div class="ist-infra" style="margin-bottom:27px;">
++  <strong>Institutional solutions matter especially when responsibility must extend beyond individual people.</strong>
++  This is particularly relevant for shared accounts, access rights, support, data protection, technical handover
++  and whether project materials will still be accessible after project closure.
++</div>
--1. Identify what applies to your project.
--2. Document the relevant decisions.
--3. Use appropriate institutional services and support where needed.
++<section class="ist-sec">
++  <div class="ist-eye" style="color:#3f6d4b;margin-bottom:4px;">STEP 1 · DESCRIBE THE NEED</div>
++  <h3>Define the requirements that infrastructure or a tool must meet</h3>
++  <p>A clear needs description makes it easier to assess existing institutional offers and avoid unsuitable one-off solutions.</p>
++  <div class="ist-grid">
++    <div class="ist-check"><strong>Function:</strong> What needs support — storage, collaboration, production, analysis, documentation, presentation or publication?</div>
++    <div class="ist-check"><strong>Users:</strong> Who will use it — an individual, internal team, external partners, participants or the public?</div>
++    <div class="ist-check"><strong>Access:</strong> Which roles need to read, edit, administer or only view?</div>
++    <div class="ist-check"><strong>Data / materials:</strong> Which formats, volumes, devices or physical resources are involved?</div>
++    <div class="ist-check"><strong>Protection needs:</strong> Are there personal, confidential, licence-restricted or otherwise sensitive materials?</div>
++    <div class="ist-check"><strong>Support:</strong> How critical is specialist or technical support for ongoing operation?</div>
++    <div class="ist-check"><strong>Export / handover:</strong> Will data, files, settings or results need to leave the system later?</div>
++    <div class="ist-check"><strong>Costs / duration:</strong> Are there recurring fees, consumables, licences or project-specific acquisition costs?</div>
++    <div class="ist-check"><strong>Availability:</strong> How long must the infrastructure remain usable and what happens after project closure?</div>
++    <div class="ist-check"><strong>Dependencies:</strong> Which other systems, accounts, rooms, devices or services must work with it?</div>
++  </div>
++</section>
--== Key questions ==
++<section class="ist-sec">
++  <div class="ist-eye" style="color:#3f6d4b;margin-bottom:4px;">KEY DISTINCTIONS</div>
++  <h3>These questions should not disappear into a single tool decision</h3>
++  <div class="ist-grid">
++    <div class="ist-infra"><strong>Tool ≠ service.</strong><br>A technical product may exist without institutional support, advice or responsibility being defined.</div>
++    <div class="ist-infra"><strong>Available ≠ suitable.</strong><br>A system being technically usable does not automatically make it appropriate for protection needs, collaboration or handover.</div>
++    <div class="ist-infra"><strong>Personal account ≠ project infrastructure.</strong><br>If a project depends on individual private or personal accounts, handover and long-term responsibility can become difficult.</div>
++    <div class="ist-infra"><strong>Storage space ≠ complete working environment.</strong><br>Collaboration may additionally require roles, versioning, approvals, documentation, backup or export options.</div>
++    <div class="ist-infra"><strong>Purchase ≠ operational readiness.</strong><br>For equipment or software, installation, maintenance, support, space, safety, training and follow-up costs can matter as much as the purchase price.</div>
++    <div class="ist-infra"><strong>Project end ≠ end of all dependencies.</strong><br>Accounts, licences, data, equipment and access often need to be handed over, closed, exported or continued deliberately.</div>
++  </div>
++</section>
--* What needs to be decided?
--* Who is responsible?
--* What needs to be documented?
--* Are there legal, ethical or technical constraints?
--* What needs to happen before the next project phase?
++<section class="ist-sec">
++  <div class="ist-eye" style="color:#3f6d4b;margin-bottom:4px;">STEP 2 · CHECK INSTITUTIONAL OPTIONS</div>
++  <h3>Review existing systems, services and specialist units first</h3>
++  <div class="ist-grid">
++    <div class="ist-step"><div class="n">01</div><h4>Assign the need to a category</h4><p>Classify the requirement as digital infrastructure, room/building service, equipment/lab or another specialist service.</p></div>
++    <div class="ist-step"><div class="n">02</div><h4>Look for existing options</h4><p>Check whether the University already provides an intended system, service or responsible specialist unit.</p></div>
++    <div class="ist-step"><div class="n">03</div><h4>Clarify specialist responsibility</h4><p>Identify who actually owns use, support, approval, maintenance or technical responsibility.</p></div>
++    <div class="ist-step"><div class="n">04</div><h4>Check the access route</h4><p>Clarify whether accounts, reservations, approvals, training or internal lead times are required.</p></div>
++    <div class="ist-step"><div class="n">05</div><h4>Check protection requirements</h4><p>Include data protection, access, confidentiality and other project-specific restrictions.</p></div>
++    <div class="ist-step"><div class="n">06</div><h4>Check costs &amp; resources</h4><p>Include licence, operating, consumable, installation or follow-up costs in the project budget.</p></div>
++    <div class="ist-step"><div class="n">07</div><h4>Clarify export and handover</h4><p>Check how files, data, settings, equipment or access can be transferred or closed when the project ends.</p></div>
++    <div class="ist-step"><div class="n">08</div><h4>Document the decision</h4><p>Record which solution was chosen, who is responsible and which dependencies remain unresolved.</p></div>
++  </div>
++</section>
--== Services & Tools ==
++<section class="ist-sec">
++  <div class="ist-eye" style="color:#3f6d4b;margin-bottom:4px;">STEP 3 · COMPARE OPTIONS</div>
++  <h3>Compare requirements and constraints systematically</h3>
++  <p>A simple comparison helps prevent choosing a tool only because it is familiar or immediately available.</p>
++  <div class="ist-table-wrap">
++    <table class="ist-table">
++      <thead><tr><th>Criterion</th><th>What to check</th><th>Why it matters</th></tr></thead>
++      <tbody>
++        <tr><td><strong>Functional fit</strong></td><td>Does the solution support the tasks and workflows the project actually needs?</td><td>Prevents tool selection without a clear project purpose.</td></tr>
++        <tr><td><strong>Institutional responsibility</strong></td><td>Is there a responsible unit, support route or defined operational owner?</td><td>Makes use and escalation routes traceable.</td></tr>
++        <tr><td><strong>Access &amp; roles</strong></td><td>Can required roles and permissions be represented appropriately?</td><td>Supports collaboration and protection needs.</td></tr>
++        <tr><td><strong>Data protection / confidentiality</strong></td><td>Is the intended use compatible with project requirements?</td><td>Prevents unsuitable storage or processing of sensitive material.</td></tr>
++        <tr><td><strong>Exportability</strong></td><td>Can files, data, metadata or settings be exported in a usable form?</td><td>Reduces dependence on a single system.</td></tr>
++        <tr><td><strong>Interoperability</strong></td><td>Does the solution work with other required tools, formats or devices?</td><td>Prevents isolated technical silos.</td></tr>
++        <tr><td><strong>Support &amp; maintenance</strong></td><td>Who helps with incidents, updates, operation or use?</td><td>Makes real operational readiness visible.</td></tr>
++        <tr><td><strong>Costs</strong></td><td>Which purchase, licence, operating, consumable or follow-up costs arise?</td><td>Connects infrastructure to realistic project planning.</td></tr>
++        <tr><td><strong>Duration</strong></td><td>Will the solution remain available throughout the project and handover period?</td><td>Prevents dependence on short-lived individual access.</td></tr>
++        <tr><td><strong>Project closure</strong></td><td>How will accounts, equipment, data, licences and access be handled at the end?</td><td>Makes handover and closure manageable.</td></tr>
++      </tbody>
++    </table>
++  </div>
++</section>
--Add links to relevant institutional services, infrastructure and tools.
++<section class="ist-sec">
++  <div class="ist-eye" style="color:#3f6d4b;margin-bottom:4px;">COMMON SCENARIOS</div>
++  <h3>Infrastructure needs look very different depending on the project</h3>
++  <div class="ist-grid">
++    <div class="ist-scenario"><h4>Shared digital working environment</h4><p>Consider accounts, roles, storage, collaboration, backup, export and handover together rather than as separate decisions.</p></div>
++    <div class="ist-scenario"><h4>Large media or research data</h4><p>Consider storage, transfer, backup, access rights, processing and any need for specialised infrastructure.</p></div>
++    <div class="ist-scenario"><h4>Equipment, workshops or labs</h4><p>Clarify availability, access rules, training, safety, consumables, maintenance and technical support.</p></div>
++    <div class="ist-scenario"><h4>Rooms &amp; building services</h4><p>Check capacity, accessibility, technical connections, setup time, safety and the relevant facility processes early.</p></div>
++    <div class="ist-scenario"><h4>Specialist software or platform</h4><p>Check licence, duration, accounts, export, technical dependencies and what happens to data or projects after closure.</p></div>
++    <div class="ist-scenario"><h4>Funded collaborative project</h4><p>Partners may bring different systems and responsibilities. Clarify shared working routes, handovers and institutional ownership early.</p></div>
++  </div>
++</section>
--== Info Sheets & Checklists ==
++<section class="ist-sec">
++  <div class="ist-eye" style="color:#3f6d4b;margin-bottom:4px;">STEP 4 · DOCUMENT THE INFRASTRUCTURE PLAN</div>
++  <h3>Keep the key systems, responsibilities and dependencies in one place</h3>
++  <p>The infrastructure plan can be part of project planning or the Data Management Plan. What matters is that technical dependencies are not only implicit knowledge.</p>
++  <div class="ist-grid">
++    <div class="ist-check"><strong>System / service:</strong> Which infrastructure or tool is being used?</div>
++    <div class="ist-check"><strong>Purpose:</strong> Which concrete project function does it support?</div>
++    <div class="ist-check"><strong>Responsible unit:</strong> Who is responsible institutionally or within the project?</div>
++    <div class="ist-check"><strong>Access route:</strong> How do team members obtain accounts, permissions, reservations or approvals?</div>
++    <div class="ist-check"><strong>Costs:</strong> Which one-off or recurring costs need to be planned?</div>
++    <div class="ist-check"><strong>Dependencies:</strong> Which equipment, rooms, software, accounts or data formats are additionally required?</div>
++    <div class="ist-check"><strong>Protection requirements:</strong> Which data-protection, confidentiality or security questions apply?</div>
++    <div class="ist-check"><strong>Export / handover:</strong> How will data, files, equipment or access be handled when the project closes?</div>
++  </div>
++</section>
--Add links to related Info Sheets, checklists and templates.
++<section class="ist-sec">
++  <div class="ist-eye" style="color:#8a4d36;margin-bottom:4px;">STOP &amp; CHECK</div>
++  <h3>Common warning signs in infrastructure and tool decisions</h3>
++  <div class="ist-grid">
++    <div class="ist-warn"><strong>The tool was chosen before the need was clear.</strong><br>The project adapts unnecessarily to a product instead of the solution supporting the task.</div>
++    <div class="ist-warn"><strong>Core project work depends on a private or personal account.</strong><br>Access, handover and institutional responsibility are at risk.</div>
++    <div class="ist-warn"><strong>No one knows the responsible specialist unit.</strong><br>There is no clear escalation route for incidents, approvals, maintenance or project closure.</div>
++    <div class="ist-warn"><strong>Export or data portability was never checked.</strong><br>Important project materials may become trapped in a system at the end.</div>
++    <div class="ist-warn"><strong>Only the purchase price was planned.</strong><br>Licence, operation, maintenance, consumables, space, safety, training or support are missing from the project plan.</div>
++    <div class="ist-warn"><strong>Technical dependencies are undocumented.</strong><br>After staff changes or project closure, it is unclear which systems are needed to understand or continue the work.</div>
++  </div>
++</section>
--== Tutorials ==
++<section class="ist-sec">
++  <div class="ist-eye" style="color:#3f6d4b;margin-bottom:4px;">SERVICES &amp; SUPPORT</div>
++  <h3>Which specialist service is responsible depends on the infrastructure type</h3>
++  <div class="ist-service-grid">
++    <div class="ist-service">
++      <strong>IT &amp; Digitalisation / ZID</strong>
++      <span>Primary specialist responsibility for digital systems, accounts, digital working environments and technical infrastructure.</span>
++    </div>
++    <div class="ist-service">
++      <strong>Facility Management</strong>
++      <span>Primary responsibility for rooms and building services and the corresponding internal processes.</span>
++    </div>
++    <div class="ist-service">
++      <strong>Relevant specialist unit</strong>
++      <span>For equipment, labs, workshops or other specialist infrastructure, responsibility remains with the designated unit.</span>
++    </div>
++    <div class="ist-service">
++      <strong>Support Kunst und Forschung (SKF)</strong>
++      <span>Coordinates infrastructure needs and internal routes for research projects, especially funded projects; specialist responsibility remains with the responsible unit.</span>
++    </div>
++  </div>
++</section>
--Add links to step-by-step tutorials for this topic.
++<section class="ist-sec">
++  <div class="ist-eye" style="color:#3f6d4b;margin-bottom:4px;">RELATED TOPICS</div>
++  <h3>Infrastructure decisions are closely connected to these project topics</h3>
++  <div class="ist-linkgrid">
++    <a class="ist-navlink" href="https://xwiki.uni-ak.ac.at/bin/view/Service%20Navigator/Art%20%26%20Research%20Services%20Navigator/Enable/Project%20Planning%20%26%20Organisation/">Project Planning &amp; Organisation</a>
++    <a class="ist-navlink" href="https://xwiki.uni-ak.ac.at/bin/view/Service%20Navigator/Art%20%26%20Research%20Services%20Navigator/Enable/Storage%2C%20Backup%20%26%20Security/">Storage, Backup &amp; Security</a>
++    <a class="ist-navlink" href="https://xwiki.uni-ak.ac.at/bin/view/Service%20Navigator/Art%20%26%20Research%20Services%20Navigator/Enable/Collaboration%20Setup/">Collaboration Setup</a>
++    <a class="ist-navlink" href="https://xwiki.uni-ak.ac.at/bin/view/Service%20Navigator/Art%20%26%20Research%20Services%20Navigator/Enable/Data%20Protection%20%26%20Ethics/">Data Protection &amp; Ethics</a>
++    <a class="ist-navlink" href="https://xwiki.uni-ak.ac.at/bin/view/Service%20Navigator/Art%20%26%20Research%20Services%20Navigator/Work%20%26%20Manage/Store%2C%20Back%20Up%20%26%20Control%20Access/">Store, Back Up &amp; Control Access</a>
++    <a class="ist-navlink" href="https://xwiki.uni-ak.ac.at/bin/view/Service%20Navigator/Art%20%26%20Research%20Services%20Navigator/Publish%20%26%20Share/Choose%20a%20Repository%20or%20Publication%20Platform/">Choose a Repository or Publication Platform</a>
++  </div>
++</section>
--== Related Topics ==
++<!-- ARSN_TRAINING_WORKSHOPS_INCLUDE_V1_START -->
++{{include reference="Service Navigator.Art & Research Services Navigator.Code.TrainingWorkshopsBlock" author="target" /}}
++<!-- ARSN_TRAINING_WORKSHOPS_INCLUDE_V1_END -->
--Add links to related pages in Enable, Work & Manage, and Publish & Share.
++<section class="ist-sec">
++  <div class="ist-eye" style="color:#3f6d4b;margin-bottom:4px;">PRACTICAL RESOURCES</div>
++  <h3>Info sheets, tutorials and templates</h3>
++  <div class="ist-resource-grid">
++    <div class="ist-resource"><strong>Info Sheets</strong><span class="ist-badge">COMING SOON</span><div style="color:#625d56;line-height:1.45;">Short guidance on selecting institutional systems, services, rooms, equipment and tools.</div></div>
++    <div class="ist-resource"><strong>Tutorials</strong><span class="ist-badge">COMING SOON</span><div style="color:#625d56;line-height:1.45;">Step-by-step workflows for needs analysis, option comparison and handover planning.</div></div>
++    <div class="ist-resource"><strong>Checklists &amp; Templates</strong><span class="ist-badge">COMING SOON</span><div style="color:#625d56;line-height:1.45;">Template for an infrastructure plan, tool comparison and technical project handover.</div></div>
++  </div>
++</section>
--== Need help? ==
++<div class="ist-info" style="margin-bottom:14px;">
++  <strong>Need help finding the right internal route?</strong>
++  Start with the specialist service responsible for the relevant infrastructure type.
++  In funded or project-based research involving several units, SKF can coordinate the project route and infrastructure dependencies.
++</div>
--Not sure what applies to your project? Contact Art & Research Services for support.
++<details style="margin-top:24px;padding-top:10px;border-top:1px solid #e3ded6;">
++  <summary style="cursor:pointer;color:#6a655e;font-size:13px;">Search terms &amp; related topics</summary>
++  <div style="margin-top:9px;color:#5c5650;font-size:12px;line-height:1.7;">
++    infrastructure · services · tools · digital systems · IT · ZID · Facility Management · rooms · building services · equipment · labs · workshops · software · platform · accounts · access rights · collaboration · storage · backup · support · maintenance · licence · export · interoperability · data protection · project handover · research infrastructure · project infrastructure
++  </div>
++</details>
--TODO: Replace this line with the central contact-form link once the form is available.
++</div>
++{{/html}}
++

Changes for page Infrastructure, Services & Tools

Summary

Details

Applications

Navigation

My Recent Modifications