EPADD

From COPTR
Revision as of 04:35, 24 October 2022 by 172.104.134.96 (talk)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
EPADD
ePADD is a software package developed by Stanford University's Special Collections & University Archives that supports archival processes around the appraisal, ingest, processing, discovery, and delivery of email archives.
Homepage:https://library.stanford.edu/projects/epadd
License:Apache 2.0
Platforms:Java
Wikidata ID:Q59652265
Output Formats:PREMIS (Preservation Metadata Implementation Strategies)
Function:Access,Appraisal,Content Profiling,Metadata Extraction,Metadata Processing
Content type:Email
Appears in COW:Appraise email and other large, unstructured text collections


Error in widget Ohloh Project: unable to write file /var/www/html/extensions/Widgets/compiled_templates/wrt67418b6a97e382_20297107




Description[edit]

From the project Github page: "ePADD is a software package developed by Stanford University's Special Collections & University Archives that supports archival processes around the appraisal, ingest, processing, discovery, and delivery of email archives.

The software is comprised of four modules:

  • Appraisal: Allows donors, dealers, and curators to easily gather and review email archives prior to transferring those files to an archival repository.
  • Processing: Provides archivists with the means to arrange and describe email archives.
  • Discovery: Provides the tools for repositories to remotely share a redacted view of their email archives with users through a web server discovery environment. (Note that this module is downloaded separately).
  • Delivery: Enables archival repositories to provide moderated full-text access to unrestricted email archives within a reading room environment."

From the Project page:

ePADD Technical Information

ePADD is written in Java and Javascript and powered by Apache Tomcat (v7.0) using Java EE Servlet API (v3.x) and Java Mail (v1.4.2). Text and metadata extraction, indexing and retrieval is performed by Apache Lucene (v4.7) and Apache Tika (v1.8). Charting and visualization is supported using the D3-based reusable chart library (v0.4.10). Oracle's Java Application Bundler and Launch4J are used for packaging on Mac and Windows platforms respectively. Other Java libraries from Apache (Lang, commons, CLI, IO, logging, etc.) are also used. JSON formatting is performed with the libraries org.json and Gson.

ePADD has implemented its own natural language processing (NLP) toolkit which is used for named entity extraction, disambiguation and other tasks. This toolkit supplants the Apache OpenNLP used in earlier beta versions of the ePADD software. We continue to use Muse as an internal library within ePADD. However, the Apache OpenNLP proved insufficient for our needs (at least for name recognition), and after various rounds of customization, we built our own named entity recognizer. This toolkit uses external datasets such as Wikipedia/DBpedia, Freebase, Geonames, OCLC FAST and LC Subject Headings/LC Name Authority File.

The project is developed with IDEs like IntelliJ Idea and Eclipse, built with Apache Maven, Ant, and custom shell scripts, and tracked using Git for source control and issue tracking. The ePADD software client is browser-based and compatible with Chrome and Firefox. It is optimized for Windows 7 SP1/10, OSX 10.12/10.13, and Ubuntu 16.04 machines, using Java 8.


User Experiences[edit]


Development Activity[edit]

All development activity is visible on GitHub: http://github.com/ePADD/epadd/commits


Release Feed[edit]

Below the last 3 release feeds:

2024-09-26 14:18:13
[tag:github.com,2008:Repository/38125452/v11.0.2 v11.0.2]
by jfarwer
2024-08-09 18:50:23
[tag:github.com,2008:Repository/38125452/v11.0.1 v11.0.1]
by jfarwer
2024-03-13 13:04:19
[tag:github.com,2008:Repository/38125452/v11.0.1-alpha v11.0.1 Alpha]
by jfarwer


Activity Feed[edit]

Below the last 5 commits: Failed to load RSS feed from https://github.com/ePADD/epadd/commits/master.atom: There was a problem during the HTTP request: 404 Not Found