Ticket #539 (new task)

Opened 5 years ago

Last modified 4 years ago

Journal definition via a XML file.

Reported by: amit Assigned to: rich
Priority: medium Milestone:
Component: ambra Version: 0.8
Keywords: journal Cc:
Blocking: Blocked By:

Description

PLoS Publishing application now utilizes the 'filter' concept of the Topaz platform to provide multiple journals within the same publishing application. A groovy script /usr/local/topaz/scripts/createjournal.groovy has been provided as part of the package to allow end-users to define their own journals. The main input for the script is an XML containing all the elements which will define a journal. Right now this is a very simple script as we do not have all the information that PLoS feels defines a journal.

Please define both the journals (PLoS ONE and CT) in separate XML files (use your own schema) containing all the elements of the journal (editors, submission policy, eISSN(?), name, etc.). This will be used to modify the createjournal.groovy script to allow easy creation of journal information in the database.

Dependency Graph

Attachments

plosone_journal.xml (4.3 kB) - added by rich on 08/14/07 18:17:13.
journal information for plos one
pctr_journal.xml (4.1 kB) - added by rich on 08/14/07 18:17:56.
journal information for pctr
pctr_journal_v2.xml (1.0 kB) - added by rich on 08/15/07 15:57:03.
pctr journal info v2
plosone_journal_v2.xml (0.9 kB) - added by rich on 08/15/07 15:57:24.
plosone journal info v2

Change History

08/14/07 18:17:13 changed by rich

  • attachment plosone_journal.xml added.

journal information for plos one

08/14/07 18:17:56 changed by rich

  • attachment pctr_journal.xml added.

journal information for pctr

08/14/07 18:19:24 changed by rich

  • owner changed from rich to amit.

I'm not really sure what to do with pctr journal information as it's not a journal. Let me know if I need to edit the files.

08/14/07 21:35:09 changed by amit

  • owner changed from amit to rich.

One quick question, which of these fields will not change once created? From a quick glance, it looks to me most of the information can change over time and hence we need to keep a version of it to identify with the articles printed under those particular parameters. So just please let me know the fields that will not change. Makes the information model easier.

(I can probably guess but think a definitive answer will be better)

08/15/07 15:57:03 changed by rich

  • attachment pctr_journal_v2.xml added.

pctr journal info v2

08/15/07 15:57:24 changed by rich

  • attachment plosone_journal_v2.xml added.

plosone journal info v2

08/15/07 15:58:28 changed by rich

  • owner changed from rich to amit.

Removed everything that could change dramatically. Hopefully publisher doesn't change addresses often.

08/21/07 10:00:49 changed by amit

  • milestone changed from 0.8 to 0.9.

Don't think we have time to change code now, but will need to utilize this for NTD. It would also help to map this to RDF and make it public information.

09/02/07 22:41:40 changed by

  • milestone deleted.

Milestone 0.9 deleted

01/17/08 11:09:58 changed by amit

  • owner changed from amit to rich.
  • priority changed from critical to medium.

Assigning this back to Rich, but probably will be jointly worked.