Add Periodicals theme

[wwelling]

References

Resolves #7

Description

There are a lot of extraneous comments that came along with overriding core dspace-angular components and modules. We will be attempting minimal changes to files copied for overriding to afford easier synchronization when merging from upstream.

Reimplements periodicals theme by customizing collection page component to list volumes and their issues in a list providing links to the complete item and search results of the items in an issue.

Instructions for Reviewers

Configure dspace-angular to point to dev environment DSpace REST API with config.dev.yml such as:

rest:
  ssl: true
  host: api-dev.library.tamu.edu
  port: 443
  nameSpace: /dspace7

Switch theme matcher to use UUID in regex until handles are supported:

  - name: periodicals
     extends: tamu
     regex: '0e87eb5c-ce4a-4e74-9d33-fcbfb5066209|4d390df8-2edf-4633-bfde-5b2df685c459'

Navigate to

Colleges and Schools / College of Liberal Arts / Department of English / Seventeenth-Century News

and

State Agencies / Texas A&M AgriLife Research / Texas Water Resources Institute / txH2O

List of changes in this PR:

• Add periodicals theme following the DSpace 7 theming guidelines.
• Customize CollectionPageComponent override

Data issues not resolved with logic:

1. txH2O has duplicate issues within a volume

2. Seventeenth-Century News has inconsistent issue numbers

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• [x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• [x] My PR passes ESLint validation using yarn lint
• [x] My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
• [ ] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• [ ] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• [ ] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• [ ] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• [ ] If my PR fixes an issue ticket, I've linked them together.