Skip to content
This repository has been archived by the owner on Jan 5, 2021. It is now read-only.

User-initiated Contact with Libraries #202

Open
ntallman opened this issue Jul 19, 2017 · 3 comments
Open

User-initiated Contact with Libraries #202

ntallman opened this issue Jul 19, 2017 · 3 comments

Comments

@ntallman
Copy link
Contributor

ntallman commented Jul 19, 2017

As a remote researcher,
I would like to contact University Libraries,
So that I can ask a question.

Acceptance Criteria: system issues and content questions start in the same spot. User has an initial question if the problem is about the system or related to content. If system question, feedback goes to product owner. If a content question, feedback goes to collection curator. (Curator name/contact will be stored with collection-level metadata, would need to lookup based on collection user is actively using at the time.)

User should see one option to initiate contact, not multiple options. Needs to be able to initiate contact to the appropriate person (context per collection) from wherever they are in CHO.

Dependent on #161

@ntallman ntallman added this to the Minimum Viable Product milestone Jul 19, 2017
@ntallman
Copy link
Contributor Author

Combines/refines #112 #141 #196 which have been closed.

@DanCoughlin
Copy link

Grab metadata from the page being viewed at the time to be able to have the proper person contacted based on the collection that is viewed. We will need a way to also enter this data and then essentially send a contact form email to a specific person group, based on the collection.

@ntallman
Copy link
Contributor Author

ntallman commented Aug 9, 2017

Systems questions can be routed to super admin user group.

In the event that the administrative collection-level metadata does not include a curator, content questions should also go to super admins, with a note that the collection does not have a designated curator.

@awead awead added the MVP label Dec 5, 2017
@awead awead modified the milestones: Minimum Viable Product, MVP 5 Dec 5, 2017
@awead awead added assigned and removed assigned labels Apr 24, 2018
@ntallman ntallman removed the MVP label Jan 25, 2019
@ntallman ntallman modified the milestones: MVP 5, 1.x Migration Ready Jan 25, 2019
@awead awead added this to Pointed in CHO Apr 15, 2019
@awead awead added the 8-points label Apr 15, 2019
@awead awead removed the pointed label May 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
CHO
  
Pointed
Development

No branches or pull requests

3 participants