Add ISBN/ISSN field to the API resource request form

[xsong9]

ISBN/ISSN is an important metadata element for a resource but it's missing from the form now. If this sounds ok to this group, our IT staff is willing to make the change and merge the code. Can you let us know if this is ok?

[cjc66]

I have no objections, and agree that it’s important!

-Carla

From: xsong9 [mailto:notifications@github.com] Sent: Wednesday, September 13, 2017 10:44 AM To: coral-erm/coral coral@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [coral-erm/coral] Add ISBN/ISSN field to the API resource request form (#291)

ISBN/ISSN is an important metadata element for a resource but it's missing from the form now. If this sounds ok to this group, our IT staff is willing to make the change and merge the code. Can you let us know if this is ok?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/coral-erm/coral/issues/291, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQixCA98ASriGd6U-xLl8VQrvTswBianks5siAZggaJpZM4PWZyK.

[SirsiDynix]http://www.sirsidynix.com/

[Facebook]http://www.facebook.com/SirsiDynix

[Twitter]http://twitter.com/sirsidynix

[LinkedIn]http://www.linkedin.com/company/sirsidynix

Carla Clark PRODUCT MANAGER I Carla.Clark@sirsidynix.com 800-288-8020 ext. 5734

[Kickstart Your RFP]https://shop.sirsidynix.com/?src=sdftr GET YOUR POWER OF LIBRARIES GEAR Shop now for Shirts, Totes, Buttons, Mugs and more! [Kickstart Your RFP]https://shop.sirsidynix.com/?src=sdftr [Kickstart Your RFP]http://go.sirsidynix.com/Using-Technology-to-Go-Beyond-the-One-Shot-SD-Webinar.html?src=sdftr UPCOMING WEBINAR Using Technology to Go Beyond the One-Shot | Sep 6th [Kickstart Your RFP]http://go.sirsidynix.com/Using-Technology-to-Go-Beyond-the-One-Shot-SD-Webinar.html?src=sdftr [Kickstart Your RFP]http://go.sirsidynix.com/Connections-Video_Connections-Video-LP-new.html?src=sdftr CHECK OUT OUR VIDEO FOR YOU Library Connections [Kickstart Your RFP]http://go.sirsidynix.com/Connections-Video_Connections-Video-LP-new.html?src=sdftr

The information contained in this e-mail is confidential, may contain our trade secrets, and may be privileged. It is intended only for the addressee(s) stated above. Any use, dissemination, distribution, publication, or coping of the information contained in this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately notify us by telephone at 801-223-5200 (or by return e-mail) and delete the e-mail from your system. No employee or agent is authorized to conclude any binding agreement on behalf of our Company with another party by email without express written confirmation by an officer of the Company. Thank you for your cooperation.

[veggiematts]

I have no objections. Since a resource can have several ISBN/ISSN, are you planning to be able to add multiple ISBN/ISSN from the form ?

[scottvieira]

This came up in discussion for us earlier this year. We have some resources that have both an ISSN and ISBN. Plus there was some interest to specify between a print and e-ISSN. I don't want to over complicate things as I too agree there should be a rudimentary "ISSN/ISBN" field. That being said, however, I'm curious if these needs have surfaced for others and whether or not we should have a conversation about adding and/or separating out these fields.

[xsong9]

We are thinking about just a combined ISBN/ISSN field, but users can add multiple numbers if needed. It'll be similar to what's in the Edit Resource window (see screenshot below). Of course people can add e-issn or e-isbn. Separating the fields may crowd the form. Let me know what y'all think. We'd like to make the change as soon as possible.

[xsong9]

[scottvieira]

@xsong9 What about having the field "Identifier" with a type? Similar to say something like Type and Alias as well as other fields, where the type(s) are identified under the Admin module. The user can define whatever identifier types they want: ISBN, E-ISBN, ISSN, E-ISSN, etc. This wouldn't crowd the form significantly, but would allow for users to use whatever identifiers they wanted.

[xsong9]

@scottvieira That is an interesting idea! But my concern is to make it consistent across CORAL, it may involve significant change in CORAL including change in the Admin, in the Edit Resource window, import tool and any other places using ISBN/ISSN. It'll be a simple change if just using the combined ISSN/ISBN filed, and users can use it for all other identifiers.

[scottvieira]

@xsong9 I share your concern about this, and I wouldn't recommend making a change like this at this time without more feedback if it required a lot of work. However, would you confirm with your programmer whether or not it would require a lot of work? There are many other fields already setup this way in CORAL. Clearly, it would require at least one more additional field in the database. If complicated and others thought this change would be useful, it could be postponed to a later time.