Archiving of Scientific Websites

Max Planck Institute for Physics, Calculating machine G3, 1960, Copyright: Archive of the Max Planck Society, Berlin.

Web designers usually build a website with user-friendliness, performance and search engine optimisation in mind. However, it is also becoming increasingly important to design for long-term accessibility and complete long-term archiving, which has an impact on structure, content, functionality and front-end presentation. So how should a website be structured if it is to provide relevant information, either online or in a web archive, for as long as possible – i.e. with a time horizon of more than 10 years, as recommended by the DFG’s Standards for Safeguarding Good Scientific Practice? And what should be considered before web publication?

Information models

Use clear and consistent information models to define the structure and organisation of your website and ensure that the information models are flexible enough to allow for future changes and enhancements. The choice of information model for the presentation of data on a website has a direct influence on digital data archiving; this should also be taken into account if different information models are used on individual web pages of a website. Each of these information models has its own significant properties that must be maintained so that the information is preserved and remains useful in the long term.

Technical

Basics

When archiving and using web archives, it must be clear that in most cases the archived website is only an approximation of the original site. If not all areas of a website can be archived, for example due to inaccessible areas, embedded content, dynamically generated content, etc., “blind spots”1 can arise for the evaluation and use of the archive. To counteract these “blind spots”, orientation and compliance with technical standards is recommended. This can improve overall access, archiving and finding of content.

Essential questions

Which web standards can be relevant for website archiving? Which technical aspects should be taken into account when building a website? What metadata should the website be labelled with?

Overview of website archiving

Website archiving means preserving the content, structure, functionality and front-end presentation(s) of a website using different approaches or web archiving tools and presenting them again later. There are different types, which are used differently depending on the requirements and objectives. The most common types are

1. Static archiving

HTML download Static HTML snapshots of the website are created and saved.

Screenshot based Screenshots of the website are created at different times to document the visual changes over time. As these are only images of the website, it is not possible to search or interact with them. Dynamically generated content or content designed for user interaction can currently often only be documented with screenshots or screencasts and additional text or audio descriptions.

2. Dynamic archiving

Crawling and scraping Web crawlers actively search the Internet or specific websites, follow links and extract content from websites. The archived websites are often saved as WARC files and often do not have the full functionality of the original website.

3. Archiving projects and organisations

There are organisations that specialise in archiving web content, such as the Wayback Machine from the Internet Archive Foundation.

4. Content management systems (CMS)

Some content management systems offer content versioning features that enable some form of archiving. The sustainability and format of the archive are not standardised and must be checked against the archive requirements.

W3C Standards

The World Wide Web Consortium (W3C) has developed a number of standards, compliance with which can ensure long-term availability. These standards ensure a better structure and consistency of websites, which in turn facilitates archiving.

Relevant W3C standards:

  1. HTML (Hypertext Markup Language) HTML is the basic building block of the web and is standardised by the W3C. The use of current HTML versions, such as HTML5, ensures a clear and standardised structure of websites, which simplifies archiving.
  2. CSS (Cascading Style Sheets) CSS is another W3C standard and is used to design the visual appearance of websites. The separation of content (HTML) and presentation (CSS) makes it easier to capture the actual content during archiving.
  3. XML (Extensible Markup Language) XML is a standard for structuring data, which can also be helpful when archiving structured information on websites.
  4. Web Annotations This W3C standard enables comments, annotations and metadata to be added to web content. This can be helpful for the documentation and interpretation of archived content.
  5. Web Components Web Components are a collection of W3C standards that facilitate the creation of reusable web components. This can rationalise the maintenance of web archives.
  6. Linked Data Linked data principles promote the networking of data on the web. In archiving, this networking can help to better understand relationships between different web content.
  7. Character encoding For correct display of content and indexing in search engines, the character encoding, i.e. the unique assignment of letters, numbers, special characters and symbols, must be clearly specified. Content should be encoded in UTF-8 as standard.

These W3C standards help to ensure the structure and consistency of web content, which in turn simplifies the recording and archiving of websites. The use of these standards supports long-term archiving and facilitates the later reconstruction of web content.

Robots

Certain types of instructions in the robots.txt file may be good for search engine crawlers, but they can prevent archiving crawlers from capturing important web page content that is critical for accurate web page recovery. For example, instructing crawlers to avoid certain directories such as CSS and JavaScript on a web page might not make much difference to search engine crawlers, but they would make a big difference to the quality of the archived record.

Sitemaps, links and navigation

A web crawler can only capture web pages that are known to it. It works by following links, which means that it can ultimately only archive pages that are accessible via links. It follows that a user using an archived website can only navigate by following links, as server-side functions such as searching in the archive do not work. Therefore, avoid relying solely on JavaScript or other techniques that could obfuscate links to navigate to a particular page and consider creating2 a comprehensive sitemap to ensure that the crawler does not miss anything and can easily search and navigate the web archive later. This makes it easier to capture and later access your website and its content. A sitemap is a structured list or file that contains information about the organisation, hierarchy and content of a website. A special type of sitemap is an XML sitemap, which is created primarily for search engines and is formatted in XML. It contains information about all relevant URLs on the website, including metadata such as the time of the last update, the frequency of changes and the priority of the pages. It is primarily intended for search engines and makes it easier for them to crawl and index the website efficiently, but is just as useful for archiving crawlers.

Stable URLs and redirection

To ensure continuity and accessibility of website recordings in web archives, it is crucial to maintain stable URLs and use redirects when necessary. The stability of a URL over time makes it possible to create a seamless series of website snapshots. If a URL is changed and no redirect to the new address is set up, the likelihood that the new URL will be saved in the next archiving crawl decreases. This effectively separates access to the archived web page before the URL change from access after the change. Web archiving tools are sensitive to URL stability, which also means that URLs with session IDs can be separated from previous captures of the same resource.

Metadata

Improving metadata enhances the readability of content for search engines, its findability and chronological categorisation in web archives. The timestamps associated with archived content in a web archive indicate when the crawler visited the page, but not necessarily when it was published or updated. Specifying the publish date or last update via the HTTP Last-Modified response header and/or the text in the document then helps users to better understand the temporal context of the content. Timestamps are also valuable in legal proceedings as they prove when the content may have been published or updated. The use of page-related titles and description elements <META> facilitates the curation of web pages by web archives, and improves the presentation of search result summaries.

Web page test for archive readiness

On the ArchiveReady.com page, the archivability of the website can be tested using HTML validity, page structure, Robots.txt, linking and sitemap, among other things. The tests in ArchiveReady.com are by no means exhaustive, but provide an initial overview and good indications of the weak points of the tested website with regard to web archiving.

File formats and databases

Although a website is perceived as a single unit, it consists of a large number of files and file types. The long-term maintenance of a website therefore also means the long-term maintenance of this diversity of types. Open standards and formats are therefore preferable to proprietary formats when building a website. Regardless of the openness of the standard, general distribution, familiarity and documentation also play a role.

Essential questions

Which file formats are used for the website? How sustainable are the file formats used? How is the data migration process organised?

Sustainable file formats

The sustainability factors of the US Library of Congress are recommended for the assessment of file formats.3 This recommends seven factors for the assessment of file formats:

1. disclosure This concerns the extent to which complete specifications and tools for validating technical completeness exist and whether they are (freely) accessible.

2. adoption by users This refers to how widespread the format is. This also includes its use as a so-called master format, i.e. for provision to end users, but also as a transport format between technical applications.

3. transparency This refers to the openness of the digital representation for direct analysis; for example, readability with a pure text editor.

4. self-documentation The documenting objects contain basic descriptive, technical and other administrative metadata.

External dependencies Degree of dependency of a particular format on a particular hardware. This also goes hand in hand with the question of anticipated complexity in dealing with future dependencies.

6. impact of patents Extent to which patents adversely affect the ability of archiving facilities to maintain certain content in a format.

7. technical protection mechanisms Implementation of mechanisms such as encryption that prevent the preservation of content by a trusted repository.

File formats

The choice of file formats for archiving is a key factor in the success (or failure) of digital archiving. In particular, it has been shown that in-house developments harbour a high risk of failure with regard to long-term availability. In contrast, it makes more sense to orientate oneself on existing standards. A standard is better than no standard.

At the same time, it is recommended that the file formats and the associated software and hardware are designed to be as open as possible and as closed as necessary. Non-proprietary formats are generally preserved in the long term thanks to the open source concept. And where this is not the case, at least the code, documentation etc. can be viewed and utilised for your own technical archiving concept.

Nevertheless, it makes sense to consider community-specific aspects of your own scientific field when choosing file formats. The handling of file formats can therefore not be generalised. It is therefore advisable to consider your own specialised community as a target group. The technical conventions of a website should also be taken into account.

When searching for specific file formats for archiving, two contact points are particularly recommended. The Library of Congress in Washington offers a comprehensive overview of long-lived file formats. The section on qualitative and functional factors in the archiving of websites is particularly recommended. The Swiss Coordination Office for the Permanent Archiving of Electronic Records (KOST) offers a comprehensive catalogue of archival file formats. The Overview of standards and guidelines in digital archiving is particularly suitable for an initial orientation in this topic.

Excursus archive format In addition to file formats suitable for archiving, there are also special file formats for archiving web applications. A quasi-standard for archiving websites is Web ARChive (.warc file).4 The WARC format offers a standardised way of saving different types of resources, such as HTML, images, stylesheets and other files, enriched with special metadata in a single archive. It is the standard format used by many archive crawlers and archive service providers.

Data migration

The point of data transfer is one of the critical moments in the archiving of websites. It marks the transition from working mode to archive mode. The content editing phase is now complete. In archive mode, practically no more content editing or revision takes place. This point in data migration is generally more of a procedural challenge than a technical one. This is because users have to say goodbye to the fact that their “own” website is no longer under their (content) control. However, this is offset by the advantage of long-term archiving and thus the availability of information and form.

The form of data migration depends heavily on the structure and technical circumstances of the website. For websites that contain many PDF files, for example, different migration strategies must be developed than for project websites that consist mainly of html elements. This also shows that archive-friendly platforms offer a long-term advantage as a basis. Widely used content management systems such as WordPress already offer archiving functions and extensive documentation. Open source systems also offer the advantage that there are usually communities with others who may have already found answers to such questions or are looking for them together. This can significantly simplify the migration of data for the archiving of websites.

Graphical representations

The reproduction of graphical elements of a website in an archived state is associated with numerous challenges. The problems usually increase exponentially with the complexity of the visual elements. The simpler the technical elements of a website are, the easier it is to archive in terms of form and content.

Essential questions

Are external extensions used? What significance do graphic elements have for the website? What meaningful information do graphic elements convey? And how can they be preserved in the long term with low technical complexity?

Reduction of external extensions

Technical elements such as extensions, plugins, external libraries, online databases etc. increase the complexity of the application. For archiving, their use means that pure bitstream preservation is not sufficient in most cases, e.g. to preserve the graphical representations of interactive maps. The interaction of the technical systems makes it necessary for the functionalities of the interfaces to be preserved.

In order to reduce such dependencies in maintenance, it is advisable to use dynamic and embedded external elements as sparingly as possible. By dispensing with plugins and individual extensions, path dependencies are avoided so that archiving is less complex and also more stable in the long term.

Reproduction of the visual impression

The visual representation of web pages is usually an essential piece of information that needs to be reproduced as completely as possible during archiving. At the same time, browsers are constantly being further developed as interpreting software for websites. In the long term, this leads to problems with the display of e.g. images, graphic elements such as menu bands, which are essential for the original impression of a website. In order to preserve the visual impression of html-based pages, KOST recommends the PDF/A-2 for Hypertext format, for example. This allows html files and their graphical interpretation to be reproduced. With PDF representation, the graphic design is retained at the time of archiving. In view of the constant further development of browser technologies, this is an aspect that should not be underestimated for the long-term archiving of scientific websites.

Strategic planning for “Look&Feel”

When planning your own website, it is therefore particularly advisable to be clear about the requirements and wishes for the graphical presentation. The more complex the design of the website, the more difficult it usually is to archive the website. It makes sense to address this conflict of objectives at an early stage in order to establish explicit guidelines and measures. In this way, your own requirements and the technical possibilities can be harmonised. If this decision is postponed and only made shortly before archiving, it is usually too late. Ultimately, this can also mean that the website is not archived after all and is therefore irrevocably deleted.

Machine readability

Artificial intelligence (AI) is in the spotlight thanks to the impressive capabilities of current language models. Intelligent chatbots impressively illustrate the current state of research and development in the field of text analysis and text generation. However, the success of AI solutions depends not only on having suitable algorithms for the respective application area, but also on having the best possible texts and data to train these language models. If texts are to be extracted from a corpus of archived websites for a research project, the design of the websites plays an important role. A website can be structured in such a way that text extraction can be carried out particularly efficiently and accurately.

Essential questions

Why is machine readability important? What aspects need to be considered in web design?

Implementing the following practices will help text extraction tools and search engines to better understand and interpret the content of your website:

1. Semantic HTML structure Use a clear, semantic HTML structure. This means using heading tags (h1, h2, h3, etc.) for headings, paragraph tags (p) for paragraphs and lists for lists. This makes it easier to identify and extract text elements.

2. Meaningful classes and IDs Use CSS classes and IDs to identify text elements, especially if they have a special meaning. This makes it easier to extract text from specific sections of the website.

3. Avoid complex layouts Overly complex layouts, especially those generated primarily by CSS and JavaScript, can make text extraction difficult. Endeavour to use a simple and understandable layout.

4. Structured metadata Add metadata such as author information, creation, publication and modification dates, and categories. This information can be helpful in extracting and understanding the context.

5. Alternative texts for media If you use images or other media, provide them with alternative text (alt text) to describe their content. This is important to understand the text content of these elements.

6. Clear separation of content Separate the main text content from secondary information such as navigation elements, adverts and so on. This can be achieved using HTML tags and CSS.

7. Use microdata and structured data Use structured data markup such as Schema.org to label important information on the website. Search engines and text extraction tools can use these markers to better understand the content.

8. Valid HTML and CSS Make sure your HTML and CSS are up to standard. Errors in the code can affect text extraction.

Web page archiving in the guidelines for good scientific practice

The long-term archiving of websites in a scientific context takes place within different normative frameworks.

Essential question

Do the guidelines in the DFG Code also apply to your own project website? Is there an institutional regulation for archiving project websites? Are there community-specific standards for website archiving?

Website archiving in the DFG Code

The DFG “Guidelines for Safeguarding Good Scientific Practice” are fundamental in the German context. According to these guidelines, scientists are obliged to preserve the underlying, central materials of their research for an appropriate period of time.5 This can also include project websites. The period usually refers to ten years after the end of the project. However, depending on the case and relevance, this period can also be (voluntarily) extended.

Institutional regulations on website archiving

At the same time, every German scientific institution has its own set of rules for good scientific practice (GWP).6 These internal rules may also clearly regulate the availability of research results beyond the end of the project. At the same time, it is important to note that the partners may be subject to different institutional regulations in co-operation projects. Such problems can be resolved through early clarification, ideally in the cooperation agreement or joint third-party funding application.

Subject-specific perspective on website archiving

Subject-specific regulations can also affect the archiving of research-related websites. For example, the DFG review boards can publish subject-specific recommendations for handling research data, which also formulate recommendations for website archiving. The subject-specific context of the research project must therefore always be taken into account when making an archiving decision.

Legal issues

Legal issues often affect the archiving of research-related websites. Based on the question of authorship, the options for dealing with the website to be archived develop. These can be decisions such as licensing, time limits or transfer of ownership.7

Essential questions

What is the ownership structure of the website? Who owns the publication and exploitation rights? Does the website have a licence? How is the transfer of the website to the archiving institution regulated? Is there a deposit contract?

Clarification of ownership rights

One of the central legal questions when archiving websites is the right of ownership: Who owns the website? Especially in a scientific context, this question often cannot be answered in a generalised way. On the one hand, a project website is usually created as part of an employment relationship. However, the employer is entitled to publication and exploitation rights. On the other hand, the author is generally entitled to the right of publication. Similarly, freedom of research exists in the Federal Republic of Germany according to GG Art. 5 Para. 3. Clarification of this situation depends on the details of the employment relationship and the respective contractual agreements.8 When outsourcing websites, it must of course also be clarified how the work of development companies and hosting service providers is reproduced when archiving. (Contractual) agreements should also be made in advance for the transfer of data and code from the service provider to the archiving institution.

At the same time, a decision must be made as to how the website is to be categorised. Is it predominantly textual in nature and can it therefore be categorised as a scientific publication? Or do aspects of databases including architectures, nesting and links predominate? In such a case, the website could also be considered a database work according to UrHrG § 4.9 Here, too, a decision can only be made on the basis of a specific example. If in doubt, please consult experts from your own institution.

Licence and licensing options

The owner can provide the website with a licence. If possible, this should be done. This legal act makes explicit which usage options are granted by the owner. As with software in general, the compatibility of licences must also be taken into account in the case of websites if external objects are reused. Depending on the context, website content and technical platform must be treated as different legal entities when archiving. In case of doubt, the legal experts at your own institution can provide advice and support.

Common addresses such as https://choosealicense.com, https://opensource.org/licenses/ etc. can provide support in the search for licences. For code components, it is always advisable to select software-specific licences. They contain a disclaimer for faulty code, which data-specific or CC licences do not.

Accessibility

The use of websites can be subject to barriers. This can be a particular challenge for people with a disability. For this reason, a website must be designed to be accessible. This is derived from EU Directive 2016/2102 on the accessibility of websites and mobile applications of public sector bodies.10 This was transposed into national law in 2019 in Regulation BITV 2.0.11 This also applies to public universities and research institutions. This applicable law must therefore be observed when designing a website.

The Web Content Accessibility Guidelines (WCAG 2) of the W3C are a useful standard for concrete implementation. With WAI-ARIA, for example, there are concrete specifications that are relevant for websites and their accessible use. At the same time, there are also many digital tools that help to assess the accessibility of a website. Examples of this include the WCAG Contrast Checker, the Web Accessibility Evaluation Tool or the BITV Test.

Deposit of the website

The depositum (from the Latin for “deposited”) of a scientific website should contain all the files, information etc. necessary for its maintenance. The act of depositing means that the website can no longer be edited by the owner. The archive mode is “read only”. As far as possible, the full rights of use to the website should also be transferred to the archiving institution.

In any case, it makes sense to conclude a deposit agreement between the website owner and the archiving institution. This creates legal certainty for both parties and sets a clear framework for the service and expectations for archiving. However, a clear legal categorisation with regard to ownership rights is necessary for such a contract. This is the only way to clarify who is authorised to conclude a legally binding deposit contract. Such an agreement can also contain restrictions on use or issues relating to usage rights. These could be, for example, access restrictions or embargo periods.

For the archiving of a website, the transfer of ownership rights may be advisable under certain circumstances. The background to this is that the preserving institution can also take curatorial measures such as updating the database and rectifying security gaps. Depending on the agreed preservation scenario and relevance, such an approach may make sense.

An archiving right on the part of libraries, interpreted as a right to redundant storage and, if necessary, transformation into other file formats, may also be covered by UrhG § 60e para. 1-3 under certain circumstances. This path should be discussed together to see whether such a path offers additional opportunities.

Data protection

Data protection aspects can also affect the long-term archiving of websites. It therefore makes sense to think about data protection as early as possible. Data protection should be taken into account as early as the design decision for a website structure and its technical solution, also with a view to long-term preservation.12

Essential questions

Has personal or sensitive data been published on the website? Is website user data available?

Data protection when archiving websites

Data protection can take effect in two directions on a scientific website. On the one hand, it can relate to the content of the project page. This may be the case for research projects with personal data, for example. In this case, the page should also not be publicly available or only available to a limited extent before the archive phase. The archive solution must also reflect this fact.

On the other hand, the technical and procedural data of the users must also be considered with regard to data protection. For example, there may be user accounts for publishing and editing with additional personal information or even local passwords. If this information is not absolutely necessary for the use of the archived website, consideration should be given to not transferring it to the archived state. One possibility could be, for example, a technical separation of the project website and user information during operation.

If in doubt, it makes sense to contact the local data protection officer. They can provide advice on further measures and their effectiveness.

Use cases

End of project

In many areas, the conception and launch of projects and associated websites can draw on a tried-and-tested toolbox. However, little thought is given to how a project ends when the funding comes to an end and what happens to the resulting websites. References are an essential part of scientific discourse and this depends on information being permanently available for analysis, replication, verification and citation. The main thing to consider here is what should primarily be preserved: The website content, the possibly separately stored research results or the user experience? Can the individual presentation layers be archived separately and reassembled in a meaningful way? In addition, before archiving, the site should be checked for any personal information that may still exist and should not be archived.

Retirement

Websites set up by individual scientists over a longer period of time often have a somewhat longer time horizon than project websites. Over the years, these develop into important contact points within the scientific community. When the operator of the website retires, however, the website should continue to be maintained. To make this possible, it is often possible for an institutional operator to take over the hosting – ideally. In an off-boarding process, the modalities of the transfer of ownership must then be clarified, such as the transfer of passwords and admin access or the transfer to other servers. It is also possible to set up a decommissioned mirror and the possible need to set up redirects so that citations and links can still be resolved. The less complex a site is structured, the easier it is to keep it online in the long term.

Data visualisation. Maps, diagrams, interactive graphics

Today, data must not only be collected, processed and analysed, but also appropriately visualised in order to be able to make statements about it. This often leads to very complex interactive representations in which text and visualisation may even adapt to the reading progress. Data visualisation is therefore a powerful tool for presenting numerical facts. However, it should be noted that complex interactive maps are difficult to maintain in the long term – the more different software components are required for visualisation, the less likely this is the case. If the result of a visualisation is a graphic, it should be created in an established format (see File format and Representations)

Checklist for website design

  • Definition of the communication goals
  • Definition of information models to be used
  • Conceptualisation of the logical website structure
  • Definition of the technology used The diversity must remain manageable in the long term
  • Definition of the file formats used Use open and widespread formats wherever possible
  • Define web design guidelines (“look & feel”) Design decisions and graphic elements have a direct influence on the long-term archivability of the website
  • Identify a web hosting provider
  • Definition of a data management plan (or at least a backup routine)
  • Conception of a versioning concept Guarantees scientific citation and prevents “content drift”
  • Data protection: Check technical concept
  • Data protection: Check design concept

Checklist for website archiving

  • Identification of a suitable web archive or infrastructure provider
  • Identification of properties of a website worth preserving Possible significant properties: Content (database content, text, etc.), presentation (graphics, map displays, etc.), structure (e.g. chronological sequence) or user experience (animations, design, look & feel)
  • Categorisation: What information must, should or can be retained
  • Metadata labelling of the content A search may not be available to a web archive
  • Clarification of property rights
  • Clarification of copyrights
  • Removal of copyrighted content
  • Checking for data protection-relevant content
  • Setting up access control and/or removal of privacy-sensitive content
  • Create end-of-project release of the website
  • Independent archiving of databases in research data repositories
  • Deposit agreement with archiving institution
  • Transfer data and software to archiving institution
  • Documentation of archived content
  • Documentation of the methods used
  • Publicising the archiving

Further information

Literature

Links

Footnotes

  1. The American Historical Review, Volume 108, Issue 3, June 2003, Pages 735-762, https://doi.org/10.1086/ahr/108.3.735. ↩︎
  2. An illustrative example of the concept of a sitemap is given in the article Rockwell, G., Day, S., Yu, J., Engel, M.: Burying Dead Projects: Depositing the Globalisation Compendium. In: Digital Humanities Quarterly, Vol. 8 Number 2, 2014, http://digitalhumanities.org. ↩︎
  3. https://www.loc.gov/preservation/digital/formats/intro/format_eval_rel.shtml#factors. ↩︎
  4. Andreas Weber and Claudia Piesche: “Datenspeicherung, -kuration und Langzeitverfügbarkeit”, in: Markus Putnings, Heike Neuroth and Janna Neumann (eds.): Praxishandbuch Forschungsdatenmanagement, 2021, https://doi.org/10.1515/9783110657807-019, p. 349. See also https://kost-ceco.ch/cms/warc.html. ↩︎
  5. DFG, Guidelines for Safeguarding good scientific practice, 2019, Guideline 17, p. 22 or https://wissenschaftliche-integritaet.de/kodex/archivierung/. ↩︎
  6. See, for example, Ludwig-Maximilians-Universität München and the Max Planck Society. ↩︎
  7. Please note that this text does not constitute legal advice but merely provides information on the subject matter without providing conclusive certainty. For legal advice, please contact your respective legal department. ↩︎
  8. BMBF: “Urheberrecht in der Wissenschaft Ein Überblick für Forschung, Lehre und Bibliotheken”, 2023, https://www.bmbf.de/SharedDocs/Publikationen/de/bmbf/1/31518_Urheberrecht_in_der_Wissenschaft.pdf?__blob=publicationFile&v=6, p. 43. ↩︎
  9. BMBF: “Urheberrecht in der Wissenschaft Ein Überblick für Forschung, Lehre und Bibliotheken”, 2023, https://www.bmbf.de/SharedDocs/Publikationen/de/bmbf/1/31518_Urheberrecht_in_der_Wissenschaft.pdf?__blob=publicationFile&v=6, p. 33. The database owner right UrhG § 87 para. 2 is also still an option. However, this right to protect investments in databases probably rarely applies in academic contexts. ↩︎
  10. Directive 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies, https://eur-lex.europa.eu/legal-content/DE/TXT/PDF/?uri=CELEX:32016L2102. ↩︎
  11. Ordinance on the creation of barrier-free information technology in accordance with the Disability Equality Act (Barrier-free Information Technology Ordinance — BITV 2.0), https://www.gesetze-im-internet.de/bitv_2_0/BJNR184300011.html. Section 2 (2.2) of the BITV 2.0 ordinance contains an exception for “archives that neither contain content that is required for active administrative procedures nor have been updated or revised after 23 September 2019″. ↩︎
  12. Matthias Bäcker and Sebastian Golla: Handreichung Datenschutz, published by the German Council for Social and Economic Data, RatSWD Output 8 (6), 2nd completely revised edition, Berlin 2020, https://doi.org/10.17620/02671.50, p. 31. ↩︎

The text was taken from: Frech, A., & Grossmann, Y. V. (2024). Das Internet vergisst doch – Handreichung für die Archivierung von wissenschaftlichen Webseiten (v1.0). Zenodo. https://doi.org/10.5281/zenodo.10556375.

previous
next