New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adapt OMP catalog management into OJS for continuous publication #1407
Comments
From @stranack, #1397 (comment):
|
I'd like to see "Sections" used for categorizing articles for continuous publishing, instead of adding a new Categories system. Any reservations there? In terms of the UI for continuous publishing, I'd love to see us accomplish the user-facing side of this by simply removing one element in the submission metadata modal. The Publication Date could then be a "scheduled posting" so it will just go live at that date: Should we peg this issue against a milestone so that it's not lost? |
Nate, I like that proposal. Nice and simple. Some journals will probably want to use both continuous publishing and issues -- effectively there would be a pool of articles without issues that would build up somewhere, and get periodically reshuffled into issues -- so rather than forcing JMs into one track or the other we might...
|
I think that we'll have a few homepage options in the default theme which allow a JM to kind of choose how they present their publishing schedule. For instance, I'm hoping that we'll have options to display the latest issue and/or a list of latest articles, and journals can choose what they want to prioritize. This may not be a 3.0 thing, but I raised some of this in that email I sent out about homepage blocks. Either way, I'm very much a fan of the idea of having a theme that's geared more directly towards continuous-publication. That's obviously a post-3.0 thing, but it makes a lot of sense to treat the frontend very differently for that model. |
It would also be great if editors of journals published on a rolling basis could have more control over when to send notifications of a newly published issue or article. If an issue is published and then articles gradually added to it, the notification can only go out when the issue is initially published or if the editor un-publishes and re-publishes it. |
We've recently been discussing using OMP's "categories" tools for organizing special collections (e.g. based on theme). |
I think using OMP's categories could work. Let's think about them as broadly as possible, as nothing more than an arbitrary collection, to which any meaning can be given.
This raises some questions:
Otherwise our only out-of-the-box display option will be something like this:
|
I'll just add that, while for some journals, being able to define a collection type would probably be useful, at CA we're just envisioning one type. The question about metadata is an interesting one: just a reminder, though, that we'll be grouping previously published articles into collections and so it would be a question of updating metadata for those articles, rather than including it in initial distribution. Also, in terms of showing a collection on the journal's homepage, we would want to display a teaser from the intro text and possibly an image, rather than the latest or top article to be included in the collection. The idea (on the homepage) is to present the collection as a unit, rather than calling attention to its constituent articles. |
There are many issues here that discuss the continuous publication model (one of the oldest issues here #382) and/or things connected to it. I am finding it hard to follow what kind of selections are being made. This is a major feature in OJS and connected to many things in the system (versioning, preprints, ahead-of-print features, DOIs, DOAJ registration and other metadata exports, OAI-PMH etc.). Maybe a clear roadmap of the planned features would be a good idea at some point before actual coding starts to happen? |
Sorry, all, didn't mean to fork the thread in a different direction! |
Not at all, @mlafl, we're constantly in the process of re-organizing this crazy thing. |
Just wanted to add a +1 to provide editors with more control over when to send notifications for newly published issues or articles. We have received requests from hosted journals that would like to send a new notification each time a new article is added to an existing, continuous publishing issue. |
It seems like there are a lot of different proposals embedded in this one. I'm going to close this for now. If you feel some part of this is still important, please consider making a proposal in the feature request category of our community forum. |
Providing the option in OJS 3 (or 3.1) to treat articles like stand-alone items (like books in OMP), catalog management could allow for a continuous publication option as well as give us some interesting content display choices on the journal home page.
Featured Articles, Spotlights, New Releases would all apply well in this scenario. Journals could also add major themes as categories or even create a volume or issue category.
The text was updated successfully, but these errors were encountered: