SlideShare una empresa de Scribd logo
1 de 36
Automated
Workflow at the
     AJR
    An “off-the-shelf”
   implementation of
 production automation

    Becky Haines
 bhaines@acr-arrs.org
The American Journal of
         Roentgenology (AJR)
   Published continuously since 1906
   Published by the American Roentgen Ray
    Society (founded in 1895)
   Self-published since the 1980s
   Online with HighWire since 2000; back
    issues to 1965
American Roentgen Ray
              Society
   $10 million organization
   About ½ of the budget is Publications
    related
   20,000+ current members; 24,000+
    current readers
   Educational focus (Annual Meeting, e.g.)
   Recently partnered/merged with American
    College of Radiology
The American Journal of
            Roentgenology (AJR)
   Largely proffered papers
       ca. 2,000 submission per year
       Multiple article types; largest category >1,000
        are original research papers
   Double-blinded peer review
       ca. 3,600 reviews per year
       CME for review offered
The American Journal of
            Roentgenology (AJR)
   Tiered editorial structure
       EIC
       12 Section Editors
       50+ Assistant Editors
       Super Reviewers (pool of ca. 100)
       1,600 Reviewers
American Roentgen Ray Society
   Publications Department

   AJR (300+ page monthly)
   AJR Integrative Imaging (80-page educational
    quarterly)
   JACR (uses EM via Elsevier)
   1 monthly CME subscription product for technologists
   Two 32-page magazines print and digital (1 monthly
    and 1 quarterly)
   1 monthly e-newsletter
   Two 300+-page book projects annually
   Assorted books, monographs, and other projects
Publications Department Services

   Product development
   Copy editing and proofreading
   Page layout and graphic design
   Project management from author to
    delivery
Publications Department Staffing
   Scholarly Editorial
       1 manager, 2 peer review, 1 production
        coordination/tracking, 5 FT copyeditors, 3 to 5 PT
        freelancers
   Magazine Editorial
       1 manager; 1 production manager, 1 editorial
        manager (TK), 2 writers
   Production
       1 manager, 2 production/graphic artists, 1 project
        manager, 1 production assistant (TK)
Automated Workflow
   Launched with Rapid Review in 2002
   Re-launched with Editorial Manager and
    Prepress/Production Manager in 2007
   Aries products selected specifically because of
    PM and enhanced references
   Configurability of the system was major selling
    point
   Semi-automated workflow
       EM/PM (xStyles for references)
       DJS Edit Express
Automated Workflow
   Staffed and Administered by Production Coordinator
   Administration rights shared among management team
   Used for AJR; separate site for AJRII
   Configurable to accommodate articles with distinct
    workflows like CME
   24/7 and seldom offline (even when we’re tired and
    would like it to be)
   Other projects run through AJR site
       Categorical Course
       A2D
       Other book projects
Automated Workflow--The Good
    Role and queue based
    Easy use of offsite freelancers
         One team member is in South Africa
    Accurate tracking and reporting
    Deadline monitoring
    Document repository
    Task and file interaction between departments
    Information sharing and research projects
    Modularization speeds production but still provides
     dashboard view
Automated Workflow—
            The Not So Good
   24/7 MEANS 24/7
   Reporting is rudimentary
   Flag system can be overwhelming if you get a bit
    too “flag happy”
   If not used correctly can create mayhem—close
    those tasks darn it!
   It’s not easy to get rid of someone in the system
    (see bullet above…sigh!)
   More options add to greater complexity; i.e.,
    configurability can = confusion for a small shop
Highly Configurable
AJR Automated Workflow
                    from Start to Finish
                                                                    Galley layout
  MS prep post-acceptance                  Copy editing
  A                               E                           P (includes image prep)




         Correction check             Front end corrections       Front end proofing
   E                              P                           E




       Galleys mail to author                Compile                 Page layout
   A                              E                           P



                                    Back end proofing and       Pages mail to author
         To notebook/press
    P                              E    page compile          A       and SE



A = Admin; E = Editorial; P = Production
Assign Translation Task to DJS
    Automated outside vendor task
    First step in our automated manuscript
     process
    Applies style and format macros
    Checks callouts and manuscript items
    Generates a styled Word document and
     tables
    Formats and validates references
Assign file prep and contact sheet
           tasks to staff
                           Allows multiple
                            staffers to work
                            on article
                            preparation
                            sequentially or
                            concurrently
                           Distributes
                            clerical or
                            technical tasks
                            appropriately
                           Files accessed
                            as needed
Assign layout task and files
View Individual’s Task Assignments

                        Monitor
                         workload
                        Reassign
                         tasks
                        Proxy and
                         complete
Assign Galley Mailing to author
Sharing files and reducing
           processing time
   Author replies are uploaded
   Copy editors have access to all files
   While proofreading, copy editors can check
    for author and section editor replies
   Allows for compression of multiple tasks into
    one
   Speeds production and minimizes task
    reassignment
Confession re Post-Production
            Tasks
                        PM offers
                         post-
                         production
                         data
                         collection
                        We haven’t
                         found the
                         time to do it
                         yet, but it’s
                         on our list
Flags and More Flags
Other Projects—Categorical
          Course
Other Projects—Categorical
          Course
Other Projects—Categorical
          Course
Other Projects—A2D
Other Projects—A2D
Other Projects—A2D
Two Sites—AJRII Pros
              Keeps divergent workflows
               truly separate
              Keeps statistics cleaner and
               easier to monitor
              Keeps EICs out of each
               others’ business
              Makes it easier to get a
               snapshot of each journal’s
               work
              Keeps smaller journal from
               getting “lost” in bigger
               journal workflow
Two Sites—AJRII Cons
                 Can be
                  overlooked in
                  daily work on
                  more frequent
                  publication
                 Workflows
                  become so
                  divergent the 2nd
                  site may not be
                  updated promptly
                  when changes
                  made
Automated Workflow Musts
 Volume = cost effective
 Know your process

 Staff resource

 Fearlessness
Things we didn’t think about when
               we started
   Numbering scheme
   Hard coded names and contacts in letters
   That we’d still cling to paper folders
   That we’d be able to respond to requests for change so
    quickly
   The system would allow us to understand our entire
    process better
        Individual or modular tasks are apparent to all
        Transparency in process encourages responsibility and
         accountability
        The system ties a bow on the package that everyone wants
Go For It, If…
   You have enough volume
   You have enough complexity (and who doesn’t
    these days!)
   You have geographically distributed staff,
    authors, or vendors (and if you don’t, you
    should)
   You want to take control of your processes
   You do your own editing and page layout or
    want to
And Even If…
   You don’t have an XML-based workflow
   You don’t use a structured pagination tool
   You send files to HighWire and they send
    them out to be formatted for their DTD
   You think you are behind the technology 8
    ball
Automated Workflow is for you:
   If you want to gain better control of your process
    and recognize improvements in:
       Time to publication--we can publish in as little as 3
        weeks if necessary
       File retrieval—no more warehouse or musty file
        folders
       Improve intra- and inter-team communication—notes,
        notes, and more notes
       Minimize errors—flags can save you
       Learn more about your process so you can keep
        improving it

Más contenido relacionado

Similar a 337 seminar4 g_rebeccahaines

Cleaning Up the Mess: Modernizing Your Dev Team’s Outdated Workflow
Cleaning Up the Mess: Modernizing Your Dev Team’s Outdated WorkflowCleaning Up the Mess: Modernizing Your Dev Team’s Outdated Workflow
Cleaning Up the Mess: Modernizing Your Dev Team’s Outdated WorkflowBohyun Kim
 
#DOAW16 - DevOps@work Roma 2016 - Databases under source control
#DOAW16 - DevOps@work Roma 2016 - Databases under source control#DOAW16 - DevOps@work Roma 2016 - Databases under source control
#DOAW16 - DevOps@work Roma 2016 - Databases under source controlAlessandro Alpi
 
Stat 5.4 Pre Sales Demo Master
Stat 5.4 Pre Sales Demo MasterStat 5.4 Pre Sales Demo Master
Stat 5.4 Pre Sales Demo Masterreachtimsq
 
Azure DevOps for Developers
Azure DevOps for DevelopersAzure DevOps for Developers
Azure DevOps for DevelopersSarah Dutkiewicz
 
Hadoop at Meebo: Lessons in the Real World
Hadoop at Meebo: Lessons in the Real WorldHadoop at Meebo: Lessons in the Real World
Hadoop at Meebo: Lessons in the Real Worldvoberoi
 
RTC & Work Item Customization Overview
RTC & Work Item Customization OverviewRTC & Work Item Customization Overview
RTC & Work Item Customization OverviewBharat Malge
 
FME World Tour 2015 - FME & Data Migration Simon McCabe
FME World Tour 2015 -  FME & Data Migration Simon McCabeFME World Tour 2015 -  FME & Data Migration Simon McCabe
FME World Tour 2015 - FME & Data Migration Simon McCabeIMGS
 
Development Practices & The Microsoft Approach
Development Practices & The Microsoft ApproachDevelopment Practices & The Microsoft Approach
Development Practices & The Microsoft ApproachSteve Lange
 
Agile and Scrum Workshop
Agile and Scrum WorkshopAgile and Scrum Workshop
Agile and Scrum WorkshopRainer Stropek
 
A Primer To Sybase Iq Development July 13
A Primer To Sybase Iq Development July 13A Primer To Sybase Iq Development July 13
A Primer To Sybase Iq Development July 13sparkwan
 
From Planning to Publishing: How Business Objects Migrated Documentation to D...
From Planning to Publishing: How Business Objects Migrated Documentation to D...From Planning to Publishing: How Business Objects Migrated Documentation to D...
From Planning to Publishing: How Business Objects Migrated Documentation to D...Scott Abel
 
Tasks Your Business Should Automate in 2022 That Just Make Sense
Tasks Your Business Should Automate in 2022 That Just Make SenseTasks Your Business Should Automate in 2022 That Just Make Sense
Tasks Your Business Should Automate in 2022 That Just Make SenseSafe Software
 

Similar a 337 seminar4 g_rebeccahaines (20)

197 ssp seminar05_murphy
197 ssp seminar05_murphy197 ssp seminar05_murphy
197 ssp seminar05_murphy
 
Cleaning Up the Mess: Modernizing Your Dev Team’s Outdated Workflow
Cleaning Up the Mess: Modernizing Your Dev Team’s Outdated WorkflowCleaning Up the Mess: Modernizing Your Dev Team’s Outdated Workflow
Cleaning Up the Mess: Modernizing Your Dev Team’s Outdated Workflow
 
#DOAW16 - DevOps@work Roma 2016 - Databases under source control
#DOAW16 - DevOps@work Roma 2016 - Databases under source control#DOAW16 - DevOps@work Roma 2016 - Databases under source control
#DOAW16 - DevOps@work Roma 2016 - Databases under source control
 
Stat 5.4 Pre Sales Demo Master
Stat 5.4 Pre Sales Demo MasterStat 5.4 Pre Sales Demo Master
Stat 5.4 Pre Sales Demo Master
 
Enterprise Task Management Solution - Q Track
Enterprise Task Management Solution - Q TrackEnterprise Task Management Solution - Q Track
Enterprise Task Management Solution - Q Track
 
Azure DevOps for Developers
Azure DevOps for DevelopersAzure DevOps for Developers
Azure DevOps for Developers
 
Cvs To Clear Case
Cvs To Clear CaseCvs To Clear Case
Cvs To Clear Case
 
Hadoop at Meebo: Lessons in the Real World
Hadoop at Meebo: Lessons in the Real WorldHadoop at Meebo: Lessons in the Real World
Hadoop at Meebo: Lessons in the Real World
 
Supporting SQLserver
Supporting SQLserverSupporting SQLserver
Supporting SQLserver
 
North east user group tour
North east user group tourNorth east user group tour
North east user group tour
 
Stat 5
Stat 5Stat 5
Stat 5
 
RTC & Work Item Customization Overview
RTC & Work Item Customization OverviewRTC & Work Item Customization Overview
RTC & Work Item Customization Overview
 
FME World Tour 2015 - FME & Data Migration Simon McCabe
FME World Tour 2015 -  FME & Data Migration Simon McCabeFME World Tour 2015 -  FME & Data Migration Simon McCabe
FME World Tour 2015 - FME & Data Migration Simon McCabe
 
Intro to Application Express
Intro to Application ExpressIntro to Application Express
Intro to Application Express
 
Development Practices & The Microsoft Approach
Development Practices & The Microsoft ApproachDevelopment Practices & The Microsoft Approach
Development Practices & The Microsoft Approach
 
Agile and Scrum Workshop
Agile and Scrum WorkshopAgile and Scrum Workshop
Agile and Scrum Workshop
 
A Primer To Sybase Iq Development July 13
A Primer To Sybase Iq Development July 13A Primer To Sybase Iq Development July 13
A Primer To Sybase Iq Development July 13
 
From Planning to Publishing: How Business Objects Migrated Documentation to D...
From Planning to Publishing: How Business Objects Migrated Documentation to D...From Planning to Publishing: How Business Objects Migrated Documentation to D...
From Planning to Publishing: How Business Objects Migrated Documentation to D...
 
Typical Developer Day
Typical Developer DayTypical Developer Day
Typical Developer Day
 
Tasks Your Business Should Automate in 2022 That Just Make Sense
Tasks Your Business Should Automate in 2022 That Just Make SenseTasks Your Business Should Automate in 2022 That Just Make Sense
Tasks Your Business Should Automate in 2022 That Just Make Sense
 

Más de Society for Scholarly Publishing

04142015 ssp webinar_theworldisflatforscholarlypublishing_caitlinmeadows
04142015 ssp webinar_theworldisflatforscholarlypublishing_caitlinmeadows04142015 ssp webinar_theworldisflatforscholarlypublishing_caitlinmeadows
04142015 ssp webinar_theworldisflatforscholarlypublishing_caitlinmeadowsSociety for Scholarly Publishing
 
04142015 ssp webinar_theworldisflatforscholarlypublishing_bruceheterick
04142015 ssp webinar_theworldisflatforscholarlypublishing_bruceheterick04142015 ssp webinar_theworldisflatforscholarlypublishing_bruceheterick
04142015 ssp webinar_theworldisflatforscholarlypublishing_bruceheterickSociety for Scholarly Publishing
 

Más de Society for Scholarly Publishing (20)

10052016 ssp seminar2_newsham
10052016 ssp seminar2_newsham10052016 ssp seminar2_newsham
10052016 ssp seminar2_newsham
 
10052016 ssp seminar2_rivera
10052016 ssp seminar2_rivera10052016 ssp seminar2_rivera
10052016 ssp seminar2_rivera
 
10052016 ssp seminar2_pesanelli
10052016 ssp seminar2_pesanelli10052016 ssp seminar2_pesanelli
10052016 ssp seminar2_pesanelli
 
10052016 ssp seminar2_harley
10052016 ssp seminar2_harley10052016 ssp seminar2_harley
10052016 ssp seminar2_harley
 
10042016 ssp seminar1_session4_myers
10042016 ssp seminar1_session4_myers10042016 ssp seminar1_session4_myers
10042016 ssp seminar1_session4_myers
 
10042016 ssp seminar1_session4_demers
10042016 ssp seminar1_session4_demers10042016 ssp seminar1_session4_demers
10042016 ssp seminar1_session4_demers
 
10042016 ssp seminar1_session4_cochran
10042016 ssp seminar1_session4_cochran10042016 ssp seminar1_session4_cochran
10042016 ssp seminar1_session4_cochran
 
10042016 ssp seminar1_session3_stanley
10042016 ssp seminar1_session3_stanley10042016 ssp seminar1_session3_stanley
10042016 ssp seminar1_session3_stanley
 
10042016 ssp seminar1_session3_ranganathan
10042016 ssp seminar1_session3_ranganathan10042016 ssp seminar1_session3_ranganathan
10042016 ssp seminar1_session3_ranganathan
 
10042016 ssp seminar1_session3_odike
10042016 ssp seminar1_session3_odike10042016 ssp seminar1_session3_odike
10042016 ssp seminar1_session3_odike
 
10042016 ssp seminar1_session3_cochran
10042016 ssp seminar1_session3_cochran10042016 ssp seminar1_session3_cochran
10042016 ssp seminar1_session3_cochran
 
10042016 ssp seminar1_session2_walker
10042016 ssp seminar1_session2_walker10042016 ssp seminar1_session2_walker
10042016 ssp seminar1_session2_walker
 
10042016 ssp seminar1_session2_ivins
10042016 ssp seminar1_session2_ivins10042016 ssp seminar1_session2_ivins
10042016 ssp seminar1_session2_ivins
 
10042016 ssp seminar1_session2_holland
10042016 ssp seminar1_session2_holland10042016 ssp seminar1_session2_holland
10042016 ssp seminar1_session2_holland
 
10042016 ssp seminar1_session1_stanley
10042016 ssp seminar1_session1_stanley10042016 ssp seminar1_session1_stanley
10042016 ssp seminar1_session1_stanley
 
10042016 ssp seminar1_session1_keane
10042016 ssp seminar1_session1_keane10042016 ssp seminar1_session1_keane
10042016 ssp seminar1_session1_keane
 
10042016 ssp seminar1_session1_ivins
10042016 ssp seminar1_session1_ivins10042016 ssp seminar1_session1_ivins
10042016 ssp seminar1_session1_ivins
 
10042016 ssp seminar1_session1_asadilari
10042016 ssp seminar1_session1_asadilari10042016 ssp seminar1_session1_asadilari
10042016 ssp seminar1_session1_asadilari
 
04142015 ssp webinar_theworldisflatforscholarlypublishing_caitlinmeadows
04142015 ssp webinar_theworldisflatforscholarlypublishing_caitlinmeadows04142015 ssp webinar_theworldisflatforscholarlypublishing_caitlinmeadows
04142015 ssp webinar_theworldisflatforscholarlypublishing_caitlinmeadows
 
04142015 ssp webinar_theworldisflatforscholarlypublishing_bruceheterick
04142015 ssp webinar_theworldisflatforscholarlypublishing_bruceheterick04142015 ssp webinar_theworldisflatforscholarlypublishing_bruceheterick
04142015 ssp webinar_theworldisflatforscholarlypublishing_bruceheterick
 

337 seminar4 g_rebeccahaines

  • 1. Automated Workflow at the AJR An “off-the-shelf” implementation of production automation Becky Haines bhaines@acr-arrs.org
  • 2. The American Journal of Roentgenology (AJR)  Published continuously since 1906  Published by the American Roentgen Ray Society (founded in 1895)  Self-published since the 1980s  Online with HighWire since 2000; back issues to 1965
  • 3. American Roentgen Ray Society  $10 million organization  About ½ of the budget is Publications related  20,000+ current members; 24,000+ current readers  Educational focus (Annual Meeting, e.g.)  Recently partnered/merged with American College of Radiology
  • 4. The American Journal of Roentgenology (AJR)  Largely proffered papers  ca. 2,000 submission per year  Multiple article types; largest category >1,000 are original research papers  Double-blinded peer review  ca. 3,600 reviews per year  CME for review offered
  • 5. The American Journal of Roentgenology (AJR)  Tiered editorial structure  EIC  12 Section Editors  50+ Assistant Editors  Super Reviewers (pool of ca. 100)  1,600 Reviewers
  • 6. American Roentgen Ray Society Publications Department  AJR (300+ page monthly)  AJR Integrative Imaging (80-page educational quarterly)  JACR (uses EM via Elsevier)  1 monthly CME subscription product for technologists  Two 32-page magazines print and digital (1 monthly and 1 quarterly)  1 monthly e-newsletter  Two 300+-page book projects annually  Assorted books, monographs, and other projects
  • 7. Publications Department Services  Product development  Copy editing and proofreading  Page layout and graphic design  Project management from author to delivery
  • 8. Publications Department Staffing  Scholarly Editorial  1 manager, 2 peer review, 1 production coordination/tracking, 5 FT copyeditors, 3 to 5 PT freelancers  Magazine Editorial  1 manager; 1 production manager, 1 editorial manager (TK), 2 writers  Production  1 manager, 2 production/graphic artists, 1 project manager, 1 production assistant (TK)
  • 9. Automated Workflow  Launched with Rapid Review in 2002  Re-launched with Editorial Manager and Prepress/Production Manager in 2007  Aries products selected specifically because of PM and enhanced references  Configurability of the system was major selling point  Semi-automated workflow  EM/PM (xStyles for references)  DJS Edit Express
  • 10. Automated Workflow  Staffed and Administered by Production Coordinator  Administration rights shared among management team  Used for AJR; separate site for AJRII  Configurable to accommodate articles with distinct workflows like CME  24/7 and seldom offline (even when we’re tired and would like it to be)  Other projects run through AJR site  Categorical Course  A2D  Other book projects
  • 11. Automated Workflow--The Good  Role and queue based  Easy use of offsite freelancers  One team member is in South Africa  Accurate tracking and reporting  Deadline monitoring  Document repository  Task and file interaction between departments  Information sharing and research projects  Modularization speeds production but still provides dashboard view
  • 12. Automated Workflow— The Not So Good  24/7 MEANS 24/7  Reporting is rudimentary  Flag system can be overwhelming if you get a bit too “flag happy”  If not used correctly can create mayhem—close those tasks darn it!  It’s not easy to get rid of someone in the system (see bullet above…sigh!)  More options add to greater complexity; i.e., configurability can = confusion for a small shop
  • 14. AJR Automated Workflow from Start to Finish Galley layout MS prep post-acceptance Copy editing A E P (includes image prep) Correction check Front end corrections Front end proofing E P E Galleys mail to author Compile Page layout A E P Back end proofing and Pages mail to author To notebook/press P E page compile A and SE A = Admin; E = Editorial; P = Production
  • 15. Assign Translation Task to DJS  Automated outside vendor task  First step in our automated manuscript process  Applies style and format macros  Checks callouts and manuscript items  Generates a styled Word document and tables  Formats and validates references
  • 16. Assign file prep and contact sheet tasks to staff  Allows multiple staffers to work on article preparation sequentially or concurrently  Distributes clerical or technical tasks appropriately  Files accessed as needed
  • 17. Assign layout task and files
  • 18. View Individual’s Task Assignments  Monitor workload  Reassign tasks  Proxy and complete
  • 20. Sharing files and reducing processing time  Author replies are uploaded  Copy editors have access to all files  While proofreading, copy editors can check for author and section editor replies  Allows for compression of multiple tasks into one  Speeds production and minimizes task reassignment
  • 21. Confession re Post-Production Tasks  PM offers post- production data collection  We haven’t found the time to do it yet, but it’s on our list
  • 22. Flags and More Flags
  • 29.
  • 30. Two Sites—AJRII Pros  Keeps divergent workflows truly separate  Keeps statistics cleaner and easier to monitor  Keeps EICs out of each others’ business  Makes it easier to get a snapshot of each journal’s work  Keeps smaller journal from getting “lost” in bigger journal workflow
  • 31. Two Sites—AJRII Cons  Can be overlooked in daily work on more frequent publication  Workflows become so divergent the 2nd site may not be updated promptly when changes made
  • 32. Automated Workflow Musts  Volume = cost effective  Know your process  Staff resource  Fearlessness
  • 33. Things we didn’t think about when we started  Numbering scheme  Hard coded names and contacts in letters  That we’d still cling to paper folders  That we’d be able to respond to requests for change so quickly  The system would allow us to understand our entire process better  Individual or modular tasks are apparent to all  Transparency in process encourages responsibility and accountability  The system ties a bow on the package that everyone wants
  • 34. Go For It, If…  You have enough volume  You have enough complexity (and who doesn’t these days!)  You have geographically distributed staff, authors, or vendors (and if you don’t, you should)  You want to take control of your processes  You do your own editing and page layout or want to
  • 35. And Even If…  You don’t have an XML-based workflow  You don’t use a structured pagination tool  You send files to HighWire and they send them out to be formatted for their DTD  You think you are behind the technology 8 ball
  • 36. Automated Workflow is for you:  If you want to gain better control of your process and recognize improvements in:  Time to publication--we can publish in as little as 3 weeks if necessary  File retrieval—no more warehouse or musty file folders  Improve intra- and inter-team communication—notes, notes, and more notes  Minimize errors—flags can save you  Learn more about your process so you can keep improving it

Notas del editor

  1. Thank you for the opportunity to present to you today. My name is Becky Haines. I'm the Senior Director of Publications for the American College of Radiology-American Roentgen Ray Society, a ca. 100-million dollar combined organization with locations in Reston VA, Philadelphia PA, and Washington DC. Despite the size of my organization, I'm going to talk about one of our journals today that is run very much like a small society publisher, which is what we were until 1 year ago when we merged with our sister organization the ACR. How many of you work on 1 journal? Fewer than 5? 10 or less? My goal today is to take you through our process of implementing automation at various steps in our internal process and highlighting the off the shelf nature of our choices and the configurability of the systems we use.
  2. We dove in head first. We took ca. 4 months to set up the system and make the move from RR to EM. Had planned for January 2007, but had to do it in February. Purposely selected a product that offered both peer review and production management. At the time, we considered EM/PM to be superior to MS Central. We made several site visits to compare. Since we controlled all of our own editorial and production work, we could time the switch and manage the resubmissions from the old system to the new system. That's not to say it wasn't difficult, but the flexibility of the EM/PM made it possible to create ms types that helped us keep track of submissions from the old vs. new systems. Staged or phased approach. A lot of vendor support and because we were early adopters and testers it was cost-effective. We ran both systems overlapping for about 6 months. We launched PM several months after EM. And we switched from Cadmus Rapid Edit to Editorial Express when we made the final cutover from RR.
  3. Tried to use it for our magazine, but discarded in favor of SharePoint Initially Staffed and Administered primarily by Production Coordinator Administration rights shared among management team Well documented and relatively easy to configure and alter based on project needs Used for AJR; separate site for AJRII Configurable to accommodate articles with distinct workflows like CME (which is an entire presentation to itself!) 24/7 and seldom offline (even when we’re tired and would like it to be) Other projects run through AJR site Categorical Course A2D Other book projects
  4. Roles allow right level of user interaction Allows easy use of offsite freelancers One team member is in South Africa Accurate tracking and reporting Deadline monitoring Document repository Allows task and file interaction between departments Allows information sharing and research projects Speeds production by allowing modularization of tasks across multiple staff working on various pieces of manuscript
  5. 24/7 MEANS 24/7 as well as global. Describe alternate contact or out of office options. Reporting is rudimentary Flag system can be overwhelming if you get a bit too “flag happy” If not used correctly can create mayhem—close those tasks darn it! This week’s example involved tasks that could not be closed because a staff person had multiple roles and the other staff person couldn’t proxy because they lacked a certain permission. It’s not easy to get rid of someone in the system (see bullet above…sigh!) More options add to greater complexity; i.e., configurability can = confusion for a small shop. Just because you can do something in the system, doesn't mean you should.
  6. Configurability = responsibility
  7. Looks simple here, but according to Aries, we make the most of the system. Not sure if they mean that as a compliment.
  8. Describe automated assignment of files to outside vendor and tracking of progres Connects EM to PM Used to be necessary to upload in EM to run through PM, but no more
  9. Describe value of modular approach and concurrent tasks
  10. Describe value of notes field and production and back up use of system. This process is allowed throughout the production flow. For actual work files Production uses our server. Clarify difference between repository and processing of work.
  11. Excellent management tool for managers as well as for managing own work
  12. Describe value of tracking author activity in the system and how our authors made the transition to working with the system
  13. Too busy to go back and fill in vol., pg. numbers etc., but hope to get to it one day and use the reporting features as a result.
  14. Show our copious list. Very useful now we can sort on it. Helps people pay attention to notes.
  15. All of the same advantages for a single project like those for a single issue of the journal New roles can be established for new editors, etc.
  16. New letters and new article types set up
  17. Invite submissions using proposal process Sometimes we do what’s expedient to get the job done; proxy on behalf of timid users and push work through the system Great to generate status reports
  18. Complex 330 case project simplified Saved 2 doctors who lost their presentations by having an image repository for them and being able to assign a task and files to them…no ftp, etc.
  19. Work with remote editor and vendor
  20. Not able to send multiple approvals to for one document, but still better than before and we can use e-mail for the last step of this process
  21. Two Sites—AJRII
  22. Allows very different processes and workflows without mucking up AJR Allows tracking and reporting without filtering
  23. Since its quarterly, it’s not in our face Slowly deviates from AJR and then we have to do a big catch up usually with Aries help
  24. You’ll need enough volume to make it cost effective You’ll need a good understanding of your process but it doesn’t need to be completely documented because the set up process will force this You’ll need a tech savvy person (hopefully more than one) who has an overall understanding of the workflow or who is willing to learn it. You’ll need to be a bit fearless re making changes because the flexibility of the system encourages it
  25. Don’t forget to change your numbering scheme at the beginning of the year and don’t start with the same number even if you change the prefix; Don’t hard code anyone’s name or contact info into any system letters if you can help it Paper folders: it’s not an age thing, it’s a convenience thing
  26. If you want to gain better control of your process and recognize improvements in: Time to publication--we can publish in as little as 3 weeks if necessary File retrieval—no more warehouse or musty file folders Improve intra- and inter-team communication—notes, notes, and more notes Minimize errors—flags can save you Learn more about your process so you can keep improving it