• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Finally, you can manage your Google Docs, uploads, and email attachments (plus Dropbox and Slack files) in one convenient place. Claim a free account, and in less than 2 minutes, Dokkio (from the makers of PBworks) can automatically organize your content for you.

View
 

Electronic Newsletters in Institutional Repository

Page history last edited by Monica 7 months, 3 weeks ago Saved with comment

The following workflow is intended for creating html files from Mailchimp-generated newsletters, for deposit in the Rice Digital Scholarship Archive. The inclusion of Perma.cc links can be applied to any project that seeks to preserve original webpage content when archiving html files.

 

  1. When designing new newsletter, make sure to include following around anything you don’t want to show up in archived version, like footer content:

    1. On the Design step, click the content block that contains the text you want to work with.

    2. Place tags *|IF:ARCHIVE_PAGE|* and *|ELSE:|* around text you don’t want to appear in the archived version. See additional details here. Use the preview function to check that the desired content doesn’t appear. NOTE: This can’t be applied to newsletters that have already been sent. 

  2. For Digital Scholarship Services newsletters, use the campaign archive page to get the html file.

    1. Before saving the file, temporarily disable the archive bar: Audience tab→Manage Audience→Settings→Publicity settings→Uncheck the Activate the "archive bar" for this list box→Save Publicity Settings. Additional details can be found here.

  3. If adding Perma.cc links, open html file in preferred editor or notepad. Login to Perma.cc; create new folder in Fondren DSS collection. Example: Fondren→DSS→DSS Newsletter→Summer 2020. This folder will house all Perma links created for the html file.

    1. Systematically work through the html file, generating Perma links, as needed. Replace original URLs with Perma links.

    2. If adding Perma links, include information in RDSA metadata. For example:

      1. dc.digitization.specifications -- “Note: In an effort to preserve the original newsletter content, URLs have been replaced with Perma.cc links, which provide an archived snapshot of the webpage at the time the newsletter was created.”
      2. dc.format.digitalOrigin --  born-digital
    3. Additional information about using Perma.cc can be found in the Perma.cc User Guide.

  4. HTML files should be “self-contained, non-dynamic HTML documents” to be stored in the RSDA. Using Perma.cc supports creating static self contained HTML documents.

 

 

 

 

Additional resources:

Comments (0)

You don't have permission to comment on this page.