140 likes | 243 Views
PIE migration: new interface with the same functionalities. Derek Mathieson Jozef Dransfield Pavel Razumovskiy Piotr Sowinski Wim Van Leersum. IT-AIS-EB :. IT-AIS-F :. Agenda. Introduction Reasons for m igration Looking for solutions Implementation Demo Q&A. Introduction.
E N D
PIE migration:new interface with the same functionalities Derek Mathieson Jozef Dransfield Pavel Razumovskiy Piotr Sowinski Wim Van Leersum IT-AIS-EB : IT-AIS-F :
Agenda • Introduction • Reasons for migration • Looking for solutions • Implementation • Demo • Q&A
Introduction • PIE purpose • A single coherent set of high quality data for Experiments, Collaborations and People Participating in these activities. • Intuitive • Reduced Oracle HR complexity
Introduction • PIE and procedures • Communication improved between services • Responsibilities and task defined across services • AIS applications evaluated and updated
Reasons for Migration • Very sensitive to your machine configuration • Does not work on Mac... • Very sensitive to OUR Oracle*HR configuration • Data placed in Oracle*HR via home made interface • Support problem: depending on one person • Overnight extraction to FOUNDATION database • Data propagation delays • Synchronization issues • Incoherence (example: data concerning institutes is initially entered in PIE and after transfer from hr is completed in Foundation)
Looking for solutions • Avoid dependencies on user machines • No local machine installation • Works on Mac / PC / Linux • Works on most browsers • Data placed in Oracle*HR via standard interface • Minimize synchronization process • Easier to maintain, database application upgrade proof
Looking for solutions • Keep PIE functionalities • “Lego building blocks” + a little bit of additional development
Foundation Solutions:Institutes & Experiments screens Done via Foundation screens Done via Foundation screens
HRT Done via Foundation screen Solutions:Persons’ screens Done via EDH screens Read only Read only Read only
Closer look Demo
Fundamental changes • Persons’ screens • Access Rights • By Screen (Not Experiment based) • Controlled through EDH Access Rights • Auditing • Shows ALL changes by Every User • Important: Do not share your password Look and Feel
Fundamental changes – cont • Institutes and Experiments • Access to application given via foundation menu • When modifying data verification against assigned roles – standard mechanism used in Foundation EXAMPLE • Done at the table level • Gives possibility of granting read-only access • Audit tool • who, when, what , old and new values • Simple lookup • History of changes • users of the tool to be defined
What are the next steps? • Tests by users (we’ll send you URL) • Collect key users feedback • Modifications if neccesary • PIE users presentation / training