Pre-release

@hangal hangal released this Nov 1, 2018 · 20 commits to master since this release

Assets 6

ePADD 7.0 beta 1

ePADD 7.0 beta 1 documentation

Releases for the appraisal, processing, and delivery modules; and the stand-alone discovery module.

More about installation can be found here.

Important: This release packages all email archives files using the BagIt specification, and is not backwards compatible with past releases prior to v.5. Users should migrate v.5 ePADD folders using the script available [here]:( https://github.com/ePADD/epadd/releases).

Release Notes

Updated

  1. A complete code review was performed prior to this release to ensure the quality of software and optimize performance.
  2. Significant improvements have been made to improve loading times, primarily through pre-computation of some tables.
  3. Search results are now stored in cache. Users should see improved loading times across the application, including loading of message results, correspondents, and lexicons.
  4. Major improvements have been made to how correspondent names are resolved.
  5. Profile, landing, and banner photos can now be uploaded as jpg as well as png.
  6. Downloading a set of messages from the message browse page will now download all messages in the current set as mbox, as well as all attachments (in original formats).
  7. An in-application correspondent list search feature, accessible from the search page, replaces the “Upload correspondents (CSV)” interface as the first step to applying a label to a set of correspondents.

Updated UI/UX

  1. Major UI refresh providing a much more intuitive and polished user experience
  2. Access to some functionality has been improved through consolidation or movement to more logical and intuitive locations. Consult the user documentation for more information.
  3. In-app help is now available on most screens.

@joshschneider joshschneider released this Sep 28, 2018 · 150 commits to master since this release

Assets 6

ePADD 6.1 documentation

Releases for the appraisal, processing, and delivery modules; and the stand-alone discovery module.

More about installation can be found here.

Important: This release packages all email archives files using the BagIt specification, and is not backwards compatible with past releases prior to v.5. Users should migrate v.5 ePADD folders using the script available here: https://github.com/ePADD/epadd/releases.

Release Notes

Reminder

In order to switch modules, the user must now navigate manually in the browser to localhost:9099/epadd/switch-module. Although less convenient for the purposes of testing and development, this change helps ensure that collection donors do not inadvertently switch modules. (#293)

Fixed

  1. Edited entities are now saved after restart (#294)
  2. Profile, landing, and banner images are now saved and correctly passed to other modules under Windows (#299)
  3. Regular expression lexicon search now works as expected (#298)
  4. Reporting a problem from Processing no longer sends you back to the Collections page. (#300)
Pre-release

@hangal hangal released this Sep 10, 2018 · 161 commits to master since this release

Assets 6

ePADD 6.1 beta

ePADD 6.1 beta documentation

Releases for the appraisal, processing, and delivery modules; and the stand-alone discovery module.

More about installation can be found here.

Important: This release packages all email archives files using the BagIt specification, and is not backwards compatible with past releases prior to v.5. Users should migrate v.5 ePADD folders using the script available here: https://github.com/ePADD/epadd/releases.

Release Notes

Updated

  1. In order to switch modules, the user must now navigate manually in the browser to localhost:9099/epadd/switch-module. Although less convenient for the purposes of testing and development, this change helps ensure that collection donors do not inadvertently switch modules (#293)

Fixed

  1. Collection details added in Processing are now saved (#265)
  2. Adding collection details in Processing no longer breaks the checksum. (#283)
  3. File size filter for Other Attachments now works correctly in all modules (#274)
  4. System labels no longer display in Discovery or Delivery (#260)
  5. Fixed errors related to editing entities in all Appraisal and Processing (#273) (#291)

@hangal hangal released this Aug 1, 2018 · 187 commits to master since this release

Assets 7

ePADD 6.0 user documentation

Releases for the appraisal, processing, and delivery modules; and the stand-alone discovery module.

More about installation can be found here.

Important: This release packages all email archives files using the BagIt specification, and is not backwards compatible with past releases prior to v.5. Users should migrate v.5 ePADD folders using the v6-bag-converter.jar script.

Release Notes

New

epadd-settings is now packaged with epadd-standalone.jar, epadd.exe, and epadd.dmg, and no longer needs to be separately downloaded and installed (#151).

Updated

Instructions for how to report bugs shared via error pages has been updated to make bug reporting more useful (#152).

The language for exporting attachments that are not recognized by Apache Tika (and therefore not indexed by ePADD) has been updated for clarity (#243).

Query Generator has been renamed to Multi-Entity Search (#240).

The email archive’s bounding dates will now ignore messages with no associated date (#242).

Messages with no associated date will be excluded from graph view (#250).

Known Issues

Attempting to import extremely large archives in OSX may cause the software to crash (#208).

Importing email with virus-infected attachments may cause an error due to the way file checksums are calculated (“Error code:null type: null”). The user can bypass this error by ensuring that their anti-virus program is set to automatically clean or delete all infected files without user intervention (#261).

Pre-release

@hangal hangal released this Jul 3, 2018 · 203 commits to master since this release

Assets 8

ePADD 6.0 Beta 1 user documentation

Releases for the appraisal, processing, and delivery modules; and the stand-alone discovery module.

These files including the epadd-settings.zip file below are required to run these modules.

More about installation can be found here.

Important: This release packages all email archives files using the BagIt specification, and is not backwards compatible with past releases prior to v.5. Users should migrate v.5 ePADD folders using the v6-bag-converter.jar script.

Please be sure to back up all previous work prior to experimenting with this software. We appreciate all testing and feedback, but please note that as a beta release, this should not yet be integrated into a production workflow.

Release Notes

New

  1. To facilitate data movement, ePADD has adopted the BagIt specification. This enables checksum verification to ensure file integrity, which may be especially helpful when verifying files shared by a donor. Users can manually verify the checksum on demand. (Github-226)

  2. Developed an integration with NYPL’s instance of Archivematica. ePADD can now identify preservation actions performed on ePADD bags by Archivematica, including filename clean-up and file migration. ePADD provides access to both original files and migrated files. Scripts created by NYPL to support this workflow are also accessible on Github (https://github.com/NYPL/amatica-epadd). (Github-190)

  3. User can now assign annotations to sets of messages. (Github-177)

  4. Introduced new multi-term search functionality, accessible from the Search interface. (Github-225)

  5. User can now export all message text (subject line and message body) as individual TXT files to support topic modeling. (Github-222)

  6. User can now export entities in Processing. The user can select whether they would like to export all entities or just particular entity types. Entities are exported as CSV and include the following fields: Entity name, number of related messages, start and end dates for related messages, entity type, and score (whether there is a direct match with an entity in DBPedia). (Github-195)

  7. User can now import and export the address book, enabling the user to edit correspondents outside of the application. This may be especially helpful with larger address books. (Github-209)

  8. User can now import and export individual lexicons, enabling the user to more easily share lexicons within and across institutions. Lexicons are exported as TXT. (Github-209)

  9. User can now import and export labels, enabling the user to more easily share general and restriction message labels within and across institutions. This may be especially helpful for establishing or standardizing local labelling practices. Label information are exported as JSON. (Github-209)

Updated

  1. User now has more control over exporting mail to MBOX in Appraisal and Processing. The user can now select whether they would like to export all mail, just restricted messages, or just non-restricted messages. (Github-221)

  2. User now has more control over exporting correspondents in Processing. In addition to exporting correspondents that have been confirmed via the Authorities interface, the user can now also export all unconfirmed correspondents. Unconfirmed correspondents are exported as CSV and include the following fields: Correspondent name, number of sent and received messages, number of mentions, and start and end dates for related messages. (Github-195)

Fixed

  1. The method for determining occurrences of keywords within a lexicon category has been updated to better align with user expectations. To take advantage of this change, we recommend that users now add quotation marks around hyphenated terms (such as “father-in-law”). (Github-223)

@chinuhub chinuhub released this May 14, 2018 · 213 commits to master since this release

Assets 7

Releases for the appraisal, processing, and delivery modules; and the stand-alone discovery module.

These files including the epadd-settings.zip file below are required to run these modules.

More about installation can be found here.

ePADD 5.0 user documentation

Important: This release is not backwards compatible with releases prior to v5.0. Please refer to the release notes for v5.0 for information about migrating from v4.1.

Updating from v5.0

  1. Move the following 5.0 folders in your user directory to a different directory (suggested name: ePADD 5.0): epadd-appraisal, epadd-processing, epadd-discovery, epadd-delivery.
  2. Copy the 5.0 epadd-settings folder to that same new directory.
  3. Run ePADD 5.1 and ingest the original mail in 5.1 Appraisal as if for the first time.
  4. Copy the following from your 5.0 Appraisal folder to the new 5.1 Appraisal folder, overwriting if asked:

        epadd-appraisal>user>sessions>AddressBook
        epadd-appraisal>user>sessions>Annotation.csv
        epadd-appraisal>user>sessions>CorrespondentAuthorities (folder)
        epadd-appraisal>user>sessions>LabelMapper folder

  1. Export from the 5.1 Appraisal to 5.1 Processing.
  2. Copy the following from your 5.0 Processing folder to the new 5.1 Processing folder, overwriting if asked:

        epadd-processing>[processing folder]>sessions>AddressBook
        epadd-processing>[processing folder]>sessions>Annotation.csv
        epadd-processing>[processing folder]>sessions>CorrespondentAuthorities (folder)
        epadd-processing>[processing folder]>sessions>LabelMapper folder

  1. Export from 5.1 Processing to 5.1 Discovery/Delivery

Fixed

DateDocument compareTo method breaks message import, affecting a small number of users. (Github #149 )

Release 5.0 introduced a new message count method intended to eliminate irregular messages which could not be read by ePADD (e.g. no headers or message body). While this method may have been more accurate, it advertantly complicated migration between release 4.1 and release 5.0. For this reason, the message count method has been reverted to the previous criteria. (Github #188 )

Migrating from release 4.1 to release 5.0 between two operating systems breaks the consistency of the message ID due to an encoding discrepancy. (Github #187 )

Name resolution algorithm improvements introduced in release 5.0 inadvertently introduced issues in resolving certain correspondent names. (Github #173 ) (Github #180 )

Entity counts do not match. (Github #207 ).

May 12, 2018

5.1

Corrected comapreTo to consider chronological ordering. Only consider…
…ing uniqueid was not sufficient to order docs in an increasing order of time

@joshschneider joshschneider released this Mar 1, 2018 · 239 commits to master since this release

Assets 7

ePADD 5.0 user documentation

Releases for the appraisal, processing, and delivery modules; and the stand-alone discovery module.

These files including the epadd-settings.zip file below, which has also been updated are required to run these modules.

More about installation can be found here.

Important: This release is not backwards compatible with past releases. A conversion tool has been developed to migrate work performed in ePADD 4.1. Please contact Peter Chan (pchan3@stanford.edu) to start the migration process. Please be sure to backup all previous work prior to beginning the migration. If you are not migrating, but you have previously installed ePADD, please be sure to completely remove all ePADD-related folders in your user directory before installing this version.

Release Notes

Updated

  1. The Lucene text search engine library has been updated to 7.2.1.

  2. Added more robust support for managing accessions. All email must now initially be imported into ePADD using the Appraisal module. All exports from Appraisal to Processing are now considered accessions, and must be added to Processing as a new collection, or added to an existing collection.

  3. Users can now also export mail from Appraisal in MBOX format.

  4. Adding an accession to an existing collection takes place from the collection details pane within a currently existing collection. The accession will be merged into the existing collection. This process may take some time, depending on multiple factors, including the size of the new accession and the size of the existing collection. Following the merger, the user will be presented with a Merge report. (ePADD-153)

  5. Added the ability to assign metadata to individual accessions within Processing, which is visible on the collection page within Processing, Discovery, and Delivery. Fields include: Accession ID, Accession Title, Accession Date, Scope and Content, Rights and Conditions, and Notes.

  6. The collection details pane in Processing, Discovery, and Delivery now includes information about the number of accessions included in the collection.

  7. Scope and content has been added as a collection metadata field within Processing, Discovery, and Delivery.

  8. Users can now define the default display name for a correspondent when editing correspondents. ePADD interprets the first name listed as the default display name. If you would prefer a different name as the default display, simply add it to the top of the list.

  9. Collection images are now added/edited within Processing from the Collection Details page. The method to add collection images within Appraisal has not changed.

  10. The mechanism for implementing actions (such as indicating that messages should be restricted, should not be transferred to the next module, or have been reviewed by the user) has changed. These actions are now implemented through the assignment of labels to individual messages or sets of messages. By default, ePADD includes three labels: Do not Transfer (not editable), Cleared for Release (not editable) and Reviewed (editable). Users can define any number of custom labels. Within Appraisal and Processing, labels can be defined as restriction labels or general labels. Restriction labels do not export to Discovery or Delivery, whereas general labels do. Restriction labels can be of several types. Messages that are restricted until a particular date, or restricted for a given time period from the date of message creation, are considered machine-actionable, as ePADD is now able to recognize when the restriction period has expired via an advanced search function. These messages will not automatically export to Discovery and Delivery. In order to export these messages, the user needs to manually assign them the label "Cleared for Release." (ePADD-147) (ePADD-166)

  11. ePADD will now prevent users from assigning a time period-based restriction label (e.g. Restrict for 25 years from date of message) to a message without dates, which can occur in case of message corruption or data loss.

  12. The mechanism for assigning actions/labels to a set of messages has changed. There is now a dedicated bulk label assignment interface, accessible from the message browse screen. Users can also set default labels for all messages from the Settings menu. Labels can be transferred between collections, similar to lexicons.

  13. ePADD now includes the ability to directly download a set of messages resulting from a search or browse action, in MBOX format, within the Appraisal, Processing, and Delivery modules. This functionality replaces the shopping cart functionality formerly included in the Delivery module.

  14. Results of cross-collection searching within Discovery are now hyperlinked and will bring the user directly to the resulting set of messages. (ePADD-158)

  15. Accession has been added as an optional search parameter under Advanced Search. Accession has also been added as a search facet on the message browsing / search results interface.

  16. Settings options and ePADD module selection are now accessed from the Help menu.

  17. Multiple collections can now be active in the same browser in different tabs.

  18. A conversion tool has been developed to help migrate work performed in ePADD 4.1 to ePADD 5.0. (ePADD-168)

Fixed

  1. The ability to upload a CSV file containing the email addresses of correspondents, and take action against that list of correspondents, has been reimplemented.

  2. The behavior of adding/editing collection metadata is now consistent.

Known Issues

  1. The Authorities interface currently supports assigning authority options to correspondents only. We plan to reintroduce persons and other entity types to the authority interface in a future release. Additionally, the authority matching algorithm has been updated to include correspondent name variants (e.g. Elizabeth and Becky) as well as alternative names as per the address book (e.g. Richard Fikes and Fikes, R.). In some cases, this is leading to a potentially excessive number of authority matches. We plan to introduce additional matching rules in the future. Finally, the DBpedia image preview on mouseover is currently not working as we are revamping this functionality.
Mar 1, 2018
Feb 27, 2018
some fixes for uniqueid calculation