Team Lead: Editorial Engagement Support - Data Migration - 12 months FTC

Apply now »

Date: May 23, 2024

Location: Pune, IN

Company: Springer Nature Group

 

About Springer Nature Group

Springer Nature opens the doors to discovery for researchers, educators, clinicians and other professionals. Every day, around the globe, our imprints, books, journals, platforms and technology solutions reach millions of people. For over 180 years our brands and imprints have been a trusted source of knowledge to these communities and today, more than ever, we see it as our responsibility to ensure that fundamental knowledge can be found, verified, understood and used by our communities – enabling them to improve outcomes, make progress, and benefit the generations that follow. Visit group.springernature.com and follow @SpringerNature / @SpringerNatureGroup

 

Job Title   :    Team Lead - Editorial Engagement Support - Data Migration - 12 months ( Fixed Term Contract)

Location   :    Pune    

Reports to:    Head of Editorial Engagement Support and Editor Data Project Manager 

 

About the Brand
 

Springer Nature Technology and Publishing Solutions, is the technology and publishing solutions arm of the Springer Nature Group. We leverage our insight in the publishing domain and acquire, produce and deliver content across media and markets using our Technology and Publishing Solutions. With a focus on technology driven solutions and deep insight in the publishing domain, Springer Nature Technology and Publishing Solutions offers a range of services that help our Group brand acquire, produce and deliver content in the most efficient ways possible. We are driven by over 1000 professionals in Technology, Research & Analysis and Marketing shared services

 

About the Role 

 

Springer Nature works with thousands of external and internal academic editors to run our journals and collections. These editors are a key driving force for strong submissions and journal growth, ensuring that rigorous and timely peer review of new manuscripts takes place. To better support our Editors, Springer Nature is building and migrating to a new central Editor Data System to store the records about our Editors. These will be used for publishing their records to our websites to meet Indexing Companies’ requirements and transacting with or for each individual. We want to ensure that our operational and analytics teams are all able to use and trust the central source.

 

 The Team Lead

 The Team Lead is a hands-on member of the Editor Data Migration Team. They also act as the coordinator of the team, with oversight of   the migration processes, workflow and progress.  They liaise with the Editor Data Project Manager and Publishing Teams.With Project   Management and Editorial Engagement guidance they will:

  • Gain an operational understanding of management and peer-review systems currently used to store Editor records for different families of publications: JFlow, Core Media, PubServ, SNAPP, Editorial Manager, eJournal Press (eJP), Manuscript Central
  • Collaborate with the Publishing teams to tidy elements of their Editor records to meet compliance standards for Editor Board page listings
  • Work with the system development project team to check the useability of the new screens and workflow
  • Incrementally migrate Editor Listing records for each publication to the Editor Data System. Where records differ between sources, resolving queries by researching and agreeing what is correct with the Publishing Teams and the Editor themselves.
  • Enrich the migrated Editor Listing records by matching them with their equivalent Editor records in peer review, identity and other operational systems, to enable data linking between systems.

 

Roles Responsibilities

1.As a Team Lead

  • Coordinate the activities of the Editor Data Migration Assistants
  • Coordinate and track progress of the migration of each publication’s data to the new Editor Data System.
  • Working with the Editor Data Project Manager to implement the migration as accurately, smoothly and swiftly as possible for our Publishing colleagues and the Editors themselves.
  • Becoming the escalation point for the team when unusual circumstances arise with Editor records, liaising with Editorial Engagement Support and Editor Data Project Manager to find the right solution for the individual.
  • Guiding the Editor Data Migration team with their proposed migration workflows and improve them together as the team gains experience.
  • Managing the relationship between the Editor Data Migration team and other Publishing and Operations teams.
  • Maintaining FAQs about the migration process as the team learns

 

As a member of the Editor Data Migration Team

2. Rationalization of Editor Data

  •  Identifying and tidying elements of data about Editors on a publication to ensure it is accurate, as complete as possible and complies with our data standards. Responsibilities include:
  • Compiling elements of Enhanced Listings and Indexing Listings so each Editor on a publication has a single copy of their record in a single place
  • Working with the Publishing Teams and conducting research to establish the correct version where records differ
  • Working together with other administrative teams, for example our Journal Editorial Office (JEO) and the SNAPP support team
  • Working with Editorial Engagement and Journal Support to keep the journal Editor Listings accurate and up to date
  • Serving as test users for the new Editor Data System as we create and confirm new screens and workflows

 

3. Journal Board Page and Collection Editor Listing Migration to Editor Data System

  •  Take ownership of the migration of a publications’ data to the new Editor Data System, ensuring that each individual is migrated completely and accurately. Responsibilities include:
  • Comparing the Editor Listing record output taken from the live website, with the website itself to check everything is captured, adding missing and enhanced elements and amending to comply with data standards
  • Migrating Editor Listing elements to Editor Data System
  • Collaborating with Publishing Teams and Editorial Engagement to jointly agree that the records are correct, complete and compliant
  • Publishing Journal Board Page / Collection Listing Page and confirming records appear correctly on new website page.

 

 4. Editor record enrichment

  • Comparing the Editor Listing for that individual on that publication with the operational system’s data set and reporting (for example Google Big Query)
  • Establishing and implementing corrections that need making where the records differ, liaising with Publishing Team
  • Capturing operational system identifier for that Editor in Editor Data System
  • Main coordination point for Editor Data Project Manager with Editor Data Migration Team
  • Collaborating with Publishing teams
  • Collaborating with Editorial Engagement Team, Editor and Reviewer Recruitment teams
  • Collaborating with system development teams
  • Collaborating with data product teams relating to operational systems

 

Educational Qualification: Educated to degree level or equivalent

 

Years of Experience: 6+years

 

Place of Work: 1201/1301, Building No. 5 (R3), Gera Commerzone, Kharadi, Pune (Working in Hybrid Model)

 

Essential

 

  • Excellent interpersonal and communication skills
  • Relationship building/teamwork
  • Works cooperatively and flexibly, supporting and learning with other members of the team
  • A high level of computer literacy – understands common software (e.g. Microsoft Office suite) and gains new software skills quickly
  • Customer service experience; customer focused mindset
  • Experience with content management and journal (meta)databases

 

Desired

 

  • Experience of communication with external editors and internal stakeholders across time zones
  • Strong organizational skills, with attention to detail
  • Ownership and ability to see tasks through to completion, working to deadlines
  • Curiosity, questioning and problem solving
  • Understanding of data in its’ context: workflow dependencies and cross-system relationships
  • Recognize when the individual circumstances of the data does not fit the standard process and escalate for decision making
  • Ability to research accurately (e.g. to find out background information about an individual to propose if records in two systems that look similar might be the same person)
  • Comfortable with some ambiguity; happy to suggest process and system improvements

 

Please submit a CV and covering letter outlining your experience and interest for the role.

 

#LI-DB1

At Springer Nature, we value the diversity of our teams and work to build an inclusive culture, where people are treated fairly and can bring their differences to work and thrive. We empower our colleagues and value their diverse perspectives as we strive to attract, nurture and develop the very best talent. Springer Nature was awarded Diversity Team of the Year at the 2022 British Diversity Awards. Find out more about our DEI work here https://group.springernature.com/gp/group/taking-responsibility/diversity-equity-inclusion

If you have any access needs related to disability, neurodivergence or a chronic condition, please contact us so we can make all necessary accommodation.

For more information about career opportunities in Springer Nature please visit https://careers.springernature.com/

Apply now »