Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Building a scalable, sustainable service with OJS


Published on

Presentation given at the OJS Forum, Edinburgh, UK, 31 July 2013

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Building a scalable, sustainable service with OJS

  1. 1.                      /  @ubiquitypress   Brian  Hole:  OJS  Forum,  Edinburgh,  31  July  2013   Building  a  scalable,  sustainable   service  with  OJS  
  2. 2.                      /  @ubiquitypress   Overview    The problem  The solution  Aspects of modification  The resulting product
  3. 3.                      /  @ubiquitypress   Problem:  needed  a  large,  scalable  journals  pla=orm     Experience  from  Elsevier,  BioMed  Central,  Dryad.     Commercial  plaLorms:     are  expensive     have  a  limited  feature  set     are  difficult  to  customise     Self-­‐built  plaLorms:     are  expensive  and  Ome-­‐consuming  to  build     require  constant  maintenance     sOll  scale  poorly  
  4. 4.                      /  @ubiquitypress   Solu>on:  invest  in  modifying  OJS     Pros:     OJS  has  80%  of  the  features  of   commercial  plaLorms     Is  good  for  individual  journals     Free  and  open  source     Cons:     Quickly  becomes  difficult  to  manage  with  mulOple  journals     Does  not  look  good  out  of  the  box     Many  features  required  by  professional  publishers  are   absent  or  very  buggy     E.g.  XML  rendering,  DOI  registraOon,  metrics  
  5. 5.                      /  @ubiquitypress   Aspects  of  modifica>on   1.  Improving  scalability   2.  IntegraOng  external  services   3.  Internal  fixes   4.  Adding  features  
  6. 6.                      /  @ubiquitypress   1.  Improving  scalability     Need  mulOple  journals  on  one  plaLorm,     with  individual  look  and  feel,  good  performance     Not  possible  with  vanilla  OJS  –  either  all  same     in  one  install,  or  mulOple  installs  required     Separated  core  files  from  customised     Built  separate  back  end  system  to  amalgamate  all  journal  data  for  reporOng,   centralised  display  and  metrics     Enabled  spreading  over  mulOple  web,  DB  and  file  servers     Results:     New  journals  can  be  rolled  out  very  quickly     Individual  journal  customisaOon  is  simple     So_ware  updates  are  quick  and  painless     Can  run  a  very  large  number  of  journals  without  performance  loss    
  7. 7.                      /  @ubiquitypress   2.  Integra>ng  external  services     XML  typese`ng  done  offshore     Typesecers  are  automaOcally  noOfied  of     arOcles  ready  for  producOon     Then  log  in  to  access  files,  liaise  with  authors     re.  correcOons,  upload  final  XML     APC  billing     IntegraOon  with  the  OAK  system  (tesOng  prototype  now,  already   expanding  it  with  own  features)     External  data  repositories     Currently  working  on  integraOon  with  Dryad  and  Dataverse     InsOtuOonal  repositories     Working  on  integraOon  with  SymplecOc,  ePrints    
  8. 8.                      /  @ubiquitypress   3.  Internal  fixes     Improved  XML  rendering     Fixed  DOI  export  to   CrossRef     Fixed  archiving  code  for   CLOCKSS     MulOple  issues  with   submission  system    
  9. 9.                      /  @ubiquitypress   4.  Added  features     Professional  customisaOon  of  look  and  feel     ConOnuous  publishing  view  of  arOcles       Special  collecOons     Improved  arOcle  informaOon:  how  to  cite,  license,  peer  review     Centrally-­‐controlled  adverOsing     ArOcle-­‐level  metrics     ArOcle  views,  downloads  (counter-­‐compliant),  citaOons     Altmetrics  (tweets,  h  likes,  Zotero  bookmarks,  Wikipedia  citaOons)     Journal  metrics:  most  recent,  most  cited     Social  media  feeds  (twicer,  blogs)     Automated  indexing  for  20+  services     Automated  deposit  of  DOIs  and  references  to  CrossRef    
  10. 10.                      /  @ubiquitypress  
  11. 11.                      /  @ubiquitypress  
  12. 12.                      /  @ubiquitypress  
  13. 13.                      /  @ubiquitypress  
  14. 14.                      /  @ubiquitypress   The  resul>ng  product    A_er  2  developer  years:    Highly  scalable,  low  cost  plaLorm    Enables  quick,  efficient  publishing  with  many  automated  aspects    Full-­‐suite  of  professional  features,  many  more  being  added    Uses:    MulOple  individual  journals  for  small  socieOes    Customised  journal  plaLorms  for  larger  socieOes,  with   income  generaOng  ability  to  enable  transiOon  to  open  access    University  Press  plaLorms  
  15. 15.                      /  @ubiquitypress   University  Presses    Aim  is  to  enable  universiOes  and  their   libraries  to  run  a  professional  press   affordably    Fully  rebranded  press  runs  on  our   infrastructure,  can  be  embedded  in   insOtuOonal  website    We  take  care  of  technology,   development,  producOon  and  final   publishing    Press/library  takes  care  of  relaOonship   with  university’s  academics    Covers  journals,  books,  data    Small  amount  of  customisaOon  cost,  rest  is   fully  funded  by  APCs  
  16. 16.                      /  @ubiquitypress   For  more  informa>on:   Any  ques)ons?   @ubiquitypress   hcp://