VALEP:About

VALEP was programmed by Maximilian Damböck and designed by Christian Damböck. It was launched in May 2021, e.g., on Daily Nous, Leiter Report and the IVC website.

Hosts, Supporters, and Funding

VALEP is located at the server valep.vc.univie.ac.at, which is hosted by the University of Vienna. The Institute Vienna Circle, is maintaining the server. Further financial support is provided by the following sources:

• FWF research grant P31716: € 16,000 for programming in 2020 and 2021, € 2,000 for data processing in 2021
• The Vienna Circle Society: € 5,000 for programming in 2021
• FWF research grant P34887: at least € 12,000 for programming (2021-2023) plus approx. € 30,000 for digitization and data processing (2021-2023)

VALEP and Phaidra

All VALEP data are mirrored in the University of Vienna's digital repository Phaidra. The staff and consultants of Phaidra support the development of VALEP, including aspects of archival science (Susanne Blumesberger), database design and the technical integration of Phaidra (Raman Ganguly), copyright issues (Seyavash Amini Khanimani), and all details of the metadata design of VALEP (Ratislav Hudak).

Cooperation Partners of VALEP

We are looking for cooperation partners among international archives that hold material on the history of Logical Empiricism. If you are interested in cooperating with VALEP as an institution, or if you are simply using VALEP for your own research and are interested in depositing your collected material, please contact Christian Damböck.

Archives of Scientific Philosophy (ASP), Hillman Library, University of Pittsburgh

The Archives of Scientific Philosophy has been sharing their electronic resources with VALEP. This includes scans produced by the ASP of the Papers of Rudolf Carnap, Carl Gustav Hempel, Richard C. Jeffrey, Hans Reichenbach, Frank Plumpton Ramsey, and Rose Rand. The material comprises about 30,000 scans and is already available in VALEP. We would like to thank Ed Galloway for his most generous support and Clinton T. Graham for transferring the files.

The Technical Implementation of VALEP

Error creating thumbnail: File missing

The technical implementation of VALEP

VALEP uses the following system architecture

• A backend that is implemented in Java - Spring-Boot and uses a PostgreSQL Database
• Additional services that include
  • an EDTF-Service (NodeJS) for parsing data entries
  • (in future implementations) services for Data Import (LaTeX, external SQL databases) inside of the Java backend
  • (in future implementations) services for transfer from LaTeX to TEI-XML and HTML (written in Python)
• Local users correspond with the backend via an Apache Webserver (Angular) and a Keycloadk - OAuth2 User Access Management

VALEP uses the following strategies for data security and long-term availability of data

• Daily data backup with the standard tools provided by the University of Vienna
• Regular data backup to non-local computers
• Persistent links via DOI
• Use of standard formats such as jpg, tiff, pdf, mp3, mp4 for electronic files and LaTeX, HTML, TEI-XML for electronic editions
• Mirroring of all data at Phaidra
• (in future implementations) integration of data on persons, institutions, locations, etc. in existing online databases such as Wikidata

The Scope and Mission of VALEP

Error creating thumbnail: File missing

VALEP is an archive management tool that is intended as a platform for the history of Logical Empiricism and related currents.

VALEP functionalities:

• (left/red part of the window) representation of the hierarchical structure of an archives, including archives, collections, digital reproductions, shelves, boxes, folders, files

• (middle/green part of the window) transformation of archival material into objects that belong to a certain document category, document type and that are uniquely identified by metadata that include title, description, author, date

• (upper right/yellow part of the window) archive nodes and documents are characterized by metadata that can be accessed in the upper right section of the screen

• (lower right/blue part of the window) Files and documents can be viewed in an integrated document viewer (already available) and the objects can be downloaded and printed (to be implemented in 2021)

VALEP records titles, descriptions and the like in the text format unicode. But some metadata categories, including date, location, language, persons, and institutions, are stored in a relational database and/or using special formats and parsing tools, e.g., EDTF for dates, and an internal tool for the mereological structure of locations. See the metadata page for the details.

The Place of VALEP within the Digital Humanities

If one expects from a digital humanities project the adoption of sophisticated statistical methods of experimental research, then VALEP does not fit the bill. Although its data pool might be used for the adoption of such methods in the future, VALEP neither now nor in the near future will be providing any tools for complex statistical evaluation.

On the other hand, one of VALEP's goals is the collection of large amounts of data. The history of Logical Empiricism, together with related currents, such as Neokantianism, French Positivism, British Empiricism, and American Pragmatism, comprises dozens of major and probably thousands of minor individuals, including academic and private scholars. Their papers can be found in public institutions and private collections, as well as additional material collected by academic and private institutions. There are thousands of manuscripts, publications, and probably millions of letters that might add significant research value in one way or another in our studies of Logical Empiricism. VALEP allows us to store, preserve, and evaluate all these sources, as soon as they become available in digital form. Then, we can search and filter them according to our needs and interests, to find the material relevant to us. This is, of course, also an important aspect of digital humanities.

VALEP's Innovative Approach

Existing tools for the management of archival sources include (1) tools that academic archives, such as the Archives of Scientific Philosophy provide; (2) open tools such as PhilArchive, where anybody can upload electronic documents; (3) tools tailored to the presentation of material of a specific origin, such as the papers of Ludwig Wittgenstein. All these tools have in common that they are more or less document oriented. They do not mirror the physical structure of an archive, but rather store documents according to a particular unit of metadata. This approach could be fruitful, if the documents are processed thoroughly and the associated metadata is clear, transparent and sufficiently complex.

However, most of the existing tools include only rudimentary metadata, and, in the case of public archives, single documents are not processed as a logical unit (e.g. letter from Otto Neurath to Rudolf Carnap from December 26, 1934), but rather, the archives provides constructed units, e.g., folders that contain several letters from Carnap to Neurath from the years 1923 to 1929. Sometimes, they might even include material unrelated to the main topic of the unit. In such cases, offering effective and meaningful metadata may not be possible at all, simply because the document units are too inconsistent.

Advantages of an Archive Oriented Presentation

When a digital archive only provides rudimentary metadata and rather ambiguous documents, it might be helpful to present the digital material in a way that reflects the physical structure and arrangement of the archive. Archives typically structure their material into collections and subcollections (or series and subseries), shelves, boxes, folders, etc. This detailed structure already represents a certain order, e.g., distinguishing between manuscripts and correspondence, providing a chronological arrangement, and/or selecting topics or correspondence partners. Despite remaining inconsistencies, archive users are usually able to work with a mnemotechnical approach, often supported by the archival finding aids. Representing the digital material according to the physical arrangement of the analog archive, might increase the transparency and usability of digital archival sources.

The Logarithmic Scale of Archival Work

Error creating thumbnail: File missing

Structuring a digital archive according to its physical organization in the analog world also yields a major pragmatic benefit. If digitized copies are stored in folders that mirror the structure of the analog archive, then you could upload the entire material, basically, with a single mouse click. The archival work involved is close to zero. On the other hand, if this archive is really large as, for example, the Schlick Papers in Haarlem, which comprises some 50,000 pages, or the Carnap Papers at the ASP, which consists of close to 100,000 pages, then you can expect to process tens of thousands of documents. If an archivist, say, is processing 20 documents per hour, this eventually will amount to several years of full time work. As you can see, we are here comparing two extremes on the scale of gains divided by working time. Most archival resources won't be processed at such a micro level, for mere lack of time and funding. However, these sources might still be available, at the level of representation of the physical structure of the repository.

The Importance of Metadata

Metadata can be needlessly complex and confusing. Therefore, a careful selection is important. For example, a document should only be associated with relevant metadata categories. Only a letter, for example, has a recipient or a place of posting, whereas a manuscript, unlike a published book or article, may not offer any publication date. So, one important aspect of making metadata adequate is by restricting certain document categories to only category-relevant metadata.

Metadata should have a consistent format. Especially crucial metadata such as date and location. Dates should be able to cover not only (several) single days but also entire months or years, and date ranges, e.g. from December 24, 1924, until October 1930. Such an approach will cover also cases where the date of a document is not clear or where a document was produced over a longer period and/or at different days or years. Locations, on the other hand, should become embedded into the mereological structure of geography. The fact that Vienna, for example, belongs to Austria and Europe but also to the Habsburg Empire and the German-speaking world, is a complex relationship structure to represent, but necessary in order to find all Viennese locations when filtering documents for Vienna, Austria, Europe, the Habsburg Empire, or the German-speaking world. Finally, in other cases, such as with individuals, institutions, languages, we can design an application with a precise search and filter function when we establish relational features and store them in predefined lists or tables. References to these predefined resources, however, should be optional, in order to keep the database structure as flexible as possible.

Archival Documents from Different Repositories: The Merging of Formats and Versions

An important aspect of merging several archival sources is that documents tend to be located not only in one folder/box held by one collection. Rather, we often find the following scenarios:

• An original document is held in archive X, whereas copies are located in other archives, e.g., carbon copies of a letter kept by the sender (which might contain relevant information that the original letter does not provide)
• Written duplicates of a document might exist, transcriptions and translations, as well as commentaries that are located at different archival repositories.
• A document might consist of several parts or chapters that, in turn, might be scattered among different archives (some of them might be the original, some might be copies, written duplicates, transcriptions, etc.)

A Note on Copyright

The international copyright legislation generally stipulates open access to metadata, whereas reproductions may be published online only if (a) the copyright was granted to the publishers by the copyright holder(s), or (b) the legal situation allows for publication without explicit transfer of copyright. There are two typical scenarios for (b): (b-1) publication of a document is possible if the death dates of all authors involved is more than 70 years ago, which turns the material into public domain; (b-2) publication is possible if the publishers can prove that the copyright holders could not be identified, despite all reasonable efforts to do so.

Copyright Protection vs. Research Access: The Flexible VALEP Approach

A logarithmic scale is emerging here. Prominent individuals, such as Carnap, Reichenbach, or Quine, could usually obtain copyright for their works easily. However, among their papers is also a wealth of material authored by others - letters TO Carnap, Quine, Reichenbach - or material that touches on privacy rights of others - e.g. Carnap discussing a specific person in a letter. Resolving all copyright issues unfolding from a Nachlass can turn into a tedious and unmanageable task. Therefore, it would be advantageous if a database could deal with these issues in a flexible way. Some material might be either removed from public access in its entirety - metadata plus reproductions - or public access will be granted (because metadata are unproblematic), but with restricted access to reproductions. Moreover, access can be restricted to the internal/non-public realm of the database, allowing access only to authorized staff.

Improving Research Tools Across Archival Repositories

To sum up, the following features would improve existing archival tools:

• representation of the physical structure of an archive (in order to support the mnemotechnical skills of researchers and make existing finding aids more useful)
• concentrating on areas with high gains and low costs first, continuing with the rest -- high gains and high costs -- only when feasible through available funding
• providing a flexible approach towards metadata categories, matching them with the pertinent document categories
• ensuring that critical metadata categories, such as date and location, use a flexible, consistent and transparent format, together with suitable parsing tools (to avoid inconsistent entries)
• implementing additional critical metadata via predefined lists and tables in a relational database setting, while keeping data fields optional whenever possible
• providing efficient tools that enable the processing of related documents held at different institutions, which can exist in a variety of formats, versions, expressions, such as carbon copies, transcriptions, or annotated duplicates
• allowing for parts of the published material to remain restricted - access to the metadata but not to the reproductions - or even restricting both metadata and reproductions, as long as copyright issues remain unsolved

VALEP as an Innovative Tool

Indeed, VALEP does provide all aforementioned features. From the start, the database design was centered around the idea of reflecting both the physical structure of an archive as well as its content. From this initial focus, all additional innovative features have naturally evolved. One example are the concepts of 'versions' and 'chapters'. They manage to intermediate between the realms of (general) documents and archives. The development of these concepts were in part inspired through feedback from archivists and the designer's own archival experience.

Who Can Use VALEP?

VALEP is available to the general public, and it's free of charge in all its applications. Typical users of VALEP might include:

• public and private institutions that hold material on the history of Logical Empiricism, using VALEP as a tool to publicize their sources and join them with other relevant material
• private researchers wanting to utilize VALEP not only to distribute and merge their sources but also to preserve them for the future
• researchers from all over the world who obtained digitized archival copies and are willing to share them with the research community, and/or want to process and organize their sources

If you are interested in using VALEP as an institution, private individual, or researcher, please contact Christian Damböck.

Future Developments

The first version of VALEP was developed in 2020/21. In spring 2022 we will add several bugfixes as well as an integration of VALEP with Phaidra: each published VALEP object will be stored in Phaidra

Future plans:

• hierarchically structured documents that may, for example, contain the chapters of a book or the entries of a diary as sub-documents
• integration of digital representations of texts and comments using LaTeX, XML, and a Git hub
• WikiData integration for persons, institutions, locations, and other metadata items
• more powerful filter tools that also allow to search the archive tree
• option to selectively restore deleted VALEP objects
• option of flagging objects in VALEP, together with advanced filter tools
• loading bundles of documents into the file viewer
• downloading JPGs within the file viewer as PDFs
• option to download the nested content of any node of the archive tree to a local computer
• XML and LaTeX download
• displaying the number of files belonging to each node of the archive tree

If you encounter any bugs, want to report problems, or have any feedback or suggestions, please contact Christian Damböck.