[UserStory] I want the project description to be configurable

[cjd2951]

User Story

Essential components

• Title describes the story
• Stakeholder type is identified
• Outcome is described
• Rationale is explicit
• Acceptance criteria are verifiable and from the perspective of the stakeholder

Story

As a Maintainer
I want the project description to be configurable rather than hard coded in the main extension class
so that I can easily reuse and modify the project description

Acceptance Criteria

(Rules or scenarios are acceptable formats.)

• Rule 1 the project description is not hard coded in Library.java
• Rule 2 the project description is accessible via environment variable

Dependencies

Depends On

#125

[jody]

Why does a maintainer want to "reuse" the "project description"?

Note that Library is not intended to be a persistent class in the product. (See Bug #117)