When we use the XML import to load data, abstracts are not required, and the "abstract" link does not appear in the table of contents. This is the desired behavior for some of our journals which don't have abstracts. However, when we try to edit the metadata the abstract field is required and we cannot make any changes (even for articles that have already been successfully imported into the system without abstracts). Also, when we load a file manually it requires an abstract. Is there a way to make abstracts optional or to work around this issue?
We are using OJS 2.2.2
Thanks!
Abstracts as required fields
Moderators: jmacgreg, michael, John, vgabler
Forum rules
This forum is meant for general questions about the usability of OJS from an everyday user's perspective: journal managers, authors, and editors are welcome to post questions here, as are librarians and other support staff. We welcome general questions about the role of OJS and how the workflow works, as well as specific function- or user-related questions.
What to do if you have general, workflow or usability questions about OJS:
1. Read the documentation. We've written documentation to cover from OJS basics to system administration and code development, and we encourage you to read it.
2. take a look at the tutorials. We will continue to add tutorials covering OJS basics as time goes on.
3. Post a question. Questions are always welcome here, but if it's a technical question you should probably post to the OJS Technical Support subforum; if you have a development question, try the OJS Development subforum.
This forum is meant for general questions about the usability of OJS from an everyday user's perspective: journal managers, authors, and editors are welcome to post questions here, as are librarians and other support staff. We welcome general questions about the role of OJS and how the workflow works, as well as specific function- or user-related questions.
What to do if you have general, workflow or usability questions about OJS:
1. Read the documentation. We've written documentation to cover from OJS basics to system administration and code development, and we encourage you to read it.
2. take a look at the tutorials. We will continue to add tutorials covering OJS basics as time goes on.
3. Post a question. Questions are always welcome here, but if it's a technical question you should probably post to the OJS Technical Support subforum; if you have a development question, try the OJS Development subforum.
4 posts
• Page 1 of 1
Abstracts as required fields
by brianlee » Wed Jan 20, 2010 8:52 am
- brianlee
- Posts: 32
- Joined: Wed Dec 13, 2006 11:42 am
Re: Abstracts as required fields
by brianlee » Wed Jan 20, 2010 9:11 am
Nevermind: I found the solution---go to the Journal Sections setup pages and check the "Do Not Require Abstracts" box....simple!
- brianlee
- Posts: 32
- Joined: Wed Dec 13, 2006 11:42 am
Re: Abstracts as required fields
by cnelson » Thu Jul 26, 2012 1:17 pm
Thanks for posting an update! This is very useful information, as we also do a lot of XML importing behind the scenes. I've read a few threads that talk about required fields, and I'm wondering: is there a way to make a field not-required for an entire journal or an entire instance of OJS (rather than just a section)? For example, the <abstract> field is often left blank, and the <firstname> field is often blank if the paper was written by the "Editors". It would be really useful to know how to turn on/off required fields for a whole site, as we host a multi-journal site and would need to do this tens of times if we had to do it per section.
Thanks!
Caitlin
Thanks!
Caitlin
- cnelson
- Posts: 17
- Joined: Mon Nov 30, 2009 3:28 pm
Re: Abstracts as required fields
by barbarah » Tue Jul 31, 2012 1:53 pm
Hi Caitlin,
I don't think there's an easy way to do this through the user interface (other than going into every section for every journal and clicking "Do not require abstracts" checkbox). If you wanted to do a wholesale change for all of your journals and all of their sections, it'd have to be done programmatically in the database, I think. We run a multi-journal installation here and the tech team ends up needing to do blanket changes directly in the database oftentimes for things that aren't enabled in the UI. (This would involve a blanket update of the sections.abstracts_not_required database field.)
Hope that helps a bit,
-Barbara
I don't think there's an easy way to do this through the user interface (other than going into every section for every journal and clicking "Do not require abstracts" checkbox). If you wanted to do a wholesale change for all of your journals and all of their sections, it'd have to be done programmatically in the database, I think. We run a multi-journal installation here and the tech team ends up needing to do blanket changes directly in the database oftentimes for things that aren't enabled in the UI. (This would involve a blanket update of the sections.abstracts_not_required database field.)
Hope that helps a bit,
-Barbara
- barbarah
- Posts: 27
- Joined: Thu Mar 24, 2011 1:25 pm
- Location: California Digital Library, Oakland, California
4 posts
• Page 1 of 1
Return to OJS Editorial Support and Discussion
Who is online
Users browsing this forum: Google [Bot] and 0 guests