The University of Houston Libraries serves over 40,000 users across its main library and 3 branches, housing 2.2 million volumes and 400,000 e-titles. It manages electronic resources using Serials Solutions, outsourcing cataloging of individual e-journals. The old process of managing individual e-journals through help desk tickets was inefficient. A new workflow was developed using a spreadsheet, Outlook emails, and color-coded statuses in Serials Solutions to track e-journals from license negotiation to cataloging. This streamlined process improves tracking, communication, and transparency across acquisitions, electronic resources, and cataloging units.
The document discusses the University of Houston Libraries' experience with various discovery tools over several years before selecting Summon. Key points include:
- UH tried several federated search tools before Summon that were difficult for users and required significant customization.
- A committee evaluated discovery tools and selected Summon due to its superior database coverage, ease of implementation, and lack of vendor bias.
- Summon has worked well out of the box but maintaining synchronization with the catalog has been challenging due to data loading restrictions.
Using technology to facilitate technical services workflowsJeannie Castro
Kelli Getz and Jeannie Castro presented on using technology to facilitate technical services workflows at their library. They discussed three projects: 1) reviewing print and online titles to set up e-access, using Outlook tasks; 2) converting print titles to online-only, using Google Drive spreadsheets; and 3) conducting three serials reviews in 2012 using Drupal, Google Drive, and WordPress. While the tools worked for individual projects, a single permanent solution was needed for ongoing workflows. They asked questions about collaboration, product evaluation and use, communication, training, and project assessment and archiving.
M.d.C. Technology is an electronics design and engineering firm founded in 2008 that specializes in innovation. They provide services including electronic design, firmware design, RF and wireless engineering, and low power design. Their mission is to help customers grow through technological innovation by integrating and complementing their skills. M.d.C. sees customers as their most important asset and focuses on innovation, investing 10% of income annually in R&D. They complete their competencies through partnerships and view customers, innovation, and partners as the three keys to success.
M.d.C. Technology is an electronics design and engineering firm founded in 2008 that specializes in innovation. They provide services including electronic design, firmware design, RF and wireless engineering, and low power design. Their mission is to help customers grow through technological innovation by integrating and complementing their skills. M.d.C. sees customers as their most important asset and focuses on innovation, investing 10% of income annually in R&D. They complete their competencies through partnerships and view customers, innovation, and partners as the three keys to success.
What does it take to manage Electronic ResourcesJeannie Castro
This document outlines the core competencies needed to manage electronic resources. It discusses that electronic resources librarians must understand technologies like hardware, networks, standards and how systems interact. They must also have research skills like data analysis and problem solving. Effective communication skills are essential to explain complex issues. Management duties involve project management, policy development and supervision. Staying aware of trends in licensing, copyright and standards is important. Most competencies apply to various roles in the electronic resources lifecycle from acquisition to discovery.
The document discusses the University of Houston Libraries' experience with various discovery tools over several years before selecting Summon. Key points include:
- UH tried several federated search tools before Summon that were difficult for users and required significant customization.
- A committee evaluated discovery tools and selected Summon due to its superior database coverage, ease of implementation, and lack of vendor bias.
- Summon has worked well out of the box but maintaining synchronization with the catalog has been challenging due to data loading restrictions.
Using technology to facilitate technical services workflowsJeannie Castro
Kelli Getz and Jeannie Castro presented on using technology to facilitate technical services workflows at their library. They discussed three projects: 1) reviewing print and online titles to set up e-access, using Outlook tasks; 2) converting print titles to online-only, using Google Drive spreadsheets; and 3) conducting three serials reviews in 2012 using Drupal, Google Drive, and WordPress. While the tools worked for individual projects, a single permanent solution was needed for ongoing workflows. They asked questions about collaboration, product evaluation and use, communication, training, and project assessment and archiving.
M.d.C. Technology is an electronics design and engineering firm founded in 2008 that specializes in innovation. They provide services including electronic design, firmware design, RF and wireless engineering, and low power design. Their mission is to help customers grow through technological innovation by integrating and complementing their skills. M.d.C. sees customers as their most important asset and focuses on innovation, investing 10% of income annually in R&D. They complete their competencies through partnerships and view customers, innovation, and partners as the three keys to success.
M.d.C. Technology is an electronics design and engineering firm founded in 2008 that specializes in innovation. They provide services including electronic design, firmware design, RF and wireless engineering, and low power design. Their mission is to help customers grow through technological innovation by integrating and complementing their skills. M.d.C. sees customers as their most important asset and focuses on innovation, investing 10% of income annually in R&D. They complete their competencies through partnerships and view customers, innovation, and partners as the three keys to success.
What does it take to manage Electronic ResourcesJeannie Castro
This document outlines the core competencies needed to manage electronic resources. It discusses that electronic resources librarians must understand technologies like hardware, networks, standards and how systems interact. They must also have research skills like data analysis and problem solving. Effective communication skills are essential to explain complex issues. Management duties involve project management, policy development and supervision. Staying aware of trends in licensing, copyright and standards is important. Most competencies apply to various roles in the electronic resources lifecycle from acquisition to discovery.
The document discusses the Big Society initiative and applying its principles to waste and resource management in the UK. It proposes giving citizens more choice and responsibility over waste services by challenging local authorities and taking over services. Citizens would be empowered with more control through referendums and experimenting with new service delivery models. The goal is to harness community enthusiasm and engagement with third sector organizations to provide scalable and family-friendly waste services.
This document summarizes student performance and demographic data from the 2011-2012 AEIS report for Worley Middle School. It shows that in 2011-2012, the majority of Worley students passed the 7th and 8th grade reading, math, writing and science tests, though social studies passage rates were lower. Worley's performance ranked in the top three of six area middle schools for most subjects tested. The report also provides data on student attendance rates, demographics, class sizes, staff demographics, and campus financial expenditures.
- The ER librarian can collaborate with subject librarians by providing usage statistics and cost-per-use calculations to help with serials reviews, and can work with serials librarians to identify titles that need format changes or issues with access and create tasks in Outlook to address problems.
- Collaboration allows the ER librarian to assist with moving print-only resources to online access when available, and revealed titles that were switched to print+online by Ebsco but never properly set up for access.
- Working together helps all parties efficiently review resources and address access issues.
The University of Houston uses III as its integrated library system and catalog which is shared with two other campuses and its law school. UH Central and two other campuses use Summon, but the law school does not. Analytics data is presented comparing use of journals, database searches, and database sessions before and after implementing Summon in fall 2010, showing increases in all categories after Summon was introduced.
The document outlines the development of a new Electronic Resource License Repository (ERLR) at the University of Houston libraries. It discusses the need for the ERLR due to confusion over license terms in the existing Electronic Resource Management system. It then describes the conceptualization, development, feedback process, population workflow, and intended usefulness of the ERLR. The ERLR was designed to make license terms and associated resources more clear and understandable for librarians and users.
This document contains a collection of jokes and puns. It includes jokes about math books, elves in school, teachers wearing sunglasses, basketball players going to jail, chickens disliking Fridays, tea bags, witches liking spelling, crossing elephants and rhinos, peeling onions, skeletons not going to balls, cows enjoying movies, numbers being afraid of each other, porcupines and cacti, watch dogs keeping time, plates serving lunch, zebras being sunburnt and red all over, skeletons going on vacation, grapes being stepped on, crossing snakes and kangaroos, boys bringing ladders to school, toilets flushing, fans leaving baseball games, and calendars having dates
This document discusses workflow templates in SAP applications. It provides an overview of available templates for different modules like asset management, finance, human resources, etc. It describes some commonly used templates and the steps to customize and enhance existing templates, including configuring organizational plans and task agents, activating event linkage, setting deadlines, and creating workflow versions. The document explains how to identify the business process, select a suitable template, and extend it if needed to meet additional requirements.
The document provides specifications for managing safety documents within a new document management system. It outlines requirements for the Livelink system, including modules, folder structure and permissions. Extensive details are provided on workflow designs to automate document revision and approval processes. Metadata fields and categories for documents are defined. Search and reporting functions within Livelink are designed to allow staff to locate documents. The specifications aim to facilitate reduced duplication, easier document location and management of document lifecycles through automated workflows.
A solution allowing the confirmation of release strategy steps in SAP using mail, a simple connector, and backed by a powerful cloud publishing component for all the purchase order related documents.
ESCAPING THE ERP USER INTERFACE
The document outlines criteria for evaluating library house-keeping software. It discusses administrative details like developer experience, documentation, support and pricing. It also covers hardware requirements, standards compliance, operating systems supported, and key modules for acquisition, cataloging, circulation, indexing and serials management. Important evaluation factors are speed, reliability, security, scalability, internationalization, portability and use of standards.
The document discusses SAP Business Workflow concepts including its purpose, terminology, advantages, and domains of application. The key purposes of SAP Business Workflow are to streamline business processes, ensure correct processes are followed, and formally define and implement processes. It provides benefits such as transparency, increased efficiency, and improved process control and monitoring.
DF2UFL 2012: Workflows: Making the MOST of Salesforce.com Native FunctionalityJennifer Phillips
DF2UFL 2012
Morning Session: Workflow - Making the MOST of Salesforce.com Native Functionality
Presented by: CloudTrigger [Silver Sponsor] Sean Wolfman
erpnext.com
On Demo Day, all team members present what they did in the month out of their own initiative. What features did they make or what documentation they wrote, or test cases, or a new product, or a new marketing initiative. It could be anything that adds value to ERPNext.
All the Demo Day presentations are made public on the erpnext blog.
This also means Open Sourcing our management. So look forward to our presentations at the end of the month and follow us to understand how this experiment is working out for us.
This document provides guidance on effectively communicating technical information to different audiences. It discusses documenting processes, systems and user manuals to create consistency, enable training and ensure compliance. It emphasizes standardizing templates and best practices. The document also explains how to customize communications by considering the audience, their needs and level of technical knowledge. It categorizes typical audience groups as co-workers, management, executives and users, and provides examples of what each would need to know to make decisions. The key message is to think about the audience and summarize information simply rather than using jargon or talking above their level in order to gain acceptance and approval for initiatives.
From selection to license negotiation through activation, libraries need the ability to track the electronic resource acquisition process and support uninterrupted workflow through multiple people and/or departments. Existing systems store fragments of information about a resource, but they don’t support management of the progress of each resource through the electronic resource acquisition maze. Stanford and Claremont have configured the JIRA and Footprints ticketing systems to address this fundamental need. Our systems facilitate efficient and complete activation of e-resources, and allow greater transparency in the acquisitions process throughout the organization. We will demonstrate the key features & functionality of our independently configured systems and invite discussion about these critical improvements to electronic resource management systems.
The document discusses using helpdesk or ticketing systems to track electronic resources acquisitions where ERMS systems failed. It describes how Stanford University Libraries and Claremont Colleges' Library implemented JIRA and eRATS in Footprints respectively to standardize their processes, define problems, and provide transparency into the status of electronic resource orders and activations. Both systems structure metadata, enable coordination between teams, and collect email trails to successfully track electronic resources acquisitions.
Quick start articles help you get set up sooner so you can begin performing the basic Business Central functions you need. The sections offer beginner's guides that help you get familiar with the features you need in Business Central. In each quick start, you'll find links to more advanced content about the functionality, should you need it. Get in Touch for Business Central Implementation: https://www.dynamicssquare.com.au/business-central-implementation/
Automate Evolve Training: Excel Workflow for Automatic RoutingPrecisely
Ready to route business processes to the right people at the right time, all while providing visibility into current and completed processes?
It’s achievable by adding a workflow to existing data templates – and that’s what we’ll cover during our Automate Evolve training on December 5, led by Tammy Lake, Senior Sales Engineer.
This session’s for you if you’re interested in taking your new or existing Excel data template to the next level. What does that look like? Adding a custom workflow that automatically routes your business processes for things like data collection, approvals, and running scripts.
You’ve already seen the value Studio scripts can bring to SAP data upload/download processes. Now, you can realize even more value by automating the manual before and after steps to complete your end-to-end business process automation.
This session will be filled with a variety of demos, including how to:
• add a workflow to an existing Excel template
• set up Excel templates to pass critical data to workflows
• set options for conditional routing and approvals
Through these demos, you’ll gain plenty of actionable takeaways that you can start implementing right away – including how to:
• interact with SAP from both business user and script developers’ perspectives
• interact with an Excel workflow from the Excel ribbon
• set different options for data validate and SAP posting, approvals, emails, and more
You’ll leave this session feeling ready and empowered to save time, boost efficiency, and change the way you work.
Automate Evolve reduces your dependency on technical resources to help create automation scenarios, remove the guesswork, and get complete visibility into business processes – and our team of experts is here to make sure you get the most out of our solution throughout the journey.
Questions? Tammy will be ready to answer them during a live Q&A at the end of the session
Project Management Tools for E-Discovery and Litigation Supportsclark22301
Two law firms shared their experiences designing and implementing project management tools for e-discovery and litigation support. Both firms started by identifying goals like tracking work, increasing visibility, and creating centralized knowledge bases. They selected web-based, customizable platforms like SharePoint that had low barriers to adoption. Their systems evolved from basic forms to track productions and data loads to more integrated workflows with alerts, reporting, and future integration plans. Key lessons included starting small to solve pressing problems and getting input from staff.
The document discusses the Big Society initiative and applying its principles to waste and resource management in the UK. It proposes giving citizens more choice and responsibility over waste services by challenging local authorities and taking over services. Citizens would be empowered with more control through referendums and experimenting with new service delivery models. The goal is to harness community enthusiasm and engagement with third sector organizations to provide scalable and family-friendly waste services.
This document summarizes student performance and demographic data from the 2011-2012 AEIS report for Worley Middle School. It shows that in 2011-2012, the majority of Worley students passed the 7th and 8th grade reading, math, writing and science tests, though social studies passage rates were lower. Worley's performance ranked in the top three of six area middle schools for most subjects tested. The report also provides data on student attendance rates, demographics, class sizes, staff demographics, and campus financial expenditures.
- The ER librarian can collaborate with subject librarians by providing usage statistics and cost-per-use calculations to help with serials reviews, and can work with serials librarians to identify titles that need format changes or issues with access and create tasks in Outlook to address problems.
- Collaboration allows the ER librarian to assist with moving print-only resources to online access when available, and revealed titles that were switched to print+online by Ebsco but never properly set up for access.
- Working together helps all parties efficiently review resources and address access issues.
The University of Houston uses III as its integrated library system and catalog which is shared with two other campuses and its law school. UH Central and two other campuses use Summon, but the law school does not. Analytics data is presented comparing use of journals, database searches, and database sessions before and after implementing Summon in fall 2010, showing increases in all categories after Summon was introduced.
The document outlines the development of a new Electronic Resource License Repository (ERLR) at the University of Houston libraries. It discusses the need for the ERLR due to confusion over license terms in the existing Electronic Resource Management system. It then describes the conceptualization, development, feedback process, population workflow, and intended usefulness of the ERLR. The ERLR was designed to make license terms and associated resources more clear and understandable for librarians and users.
This document contains a collection of jokes and puns. It includes jokes about math books, elves in school, teachers wearing sunglasses, basketball players going to jail, chickens disliking Fridays, tea bags, witches liking spelling, crossing elephants and rhinos, peeling onions, skeletons not going to balls, cows enjoying movies, numbers being afraid of each other, porcupines and cacti, watch dogs keeping time, plates serving lunch, zebras being sunburnt and red all over, skeletons going on vacation, grapes being stepped on, crossing snakes and kangaroos, boys bringing ladders to school, toilets flushing, fans leaving baseball games, and calendars having dates
This document discusses workflow templates in SAP applications. It provides an overview of available templates for different modules like asset management, finance, human resources, etc. It describes some commonly used templates and the steps to customize and enhance existing templates, including configuring organizational plans and task agents, activating event linkage, setting deadlines, and creating workflow versions. The document explains how to identify the business process, select a suitable template, and extend it if needed to meet additional requirements.
The document provides specifications for managing safety documents within a new document management system. It outlines requirements for the Livelink system, including modules, folder structure and permissions. Extensive details are provided on workflow designs to automate document revision and approval processes. Metadata fields and categories for documents are defined. Search and reporting functions within Livelink are designed to allow staff to locate documents. The specifications aim to facilitate reduced duplication, easier document location and management of document lifecycles through automated workflows.
A solution allowing the confirmation of release strategy steps in SAP using mail, a simple connector, and backed by a powerful cloud publishing component for all the purchase order related documents.
ESCAPING THE ERP USER INTERFACE
The document outlines criteria for evaluating library house-keeping software. It discusses administrative details like developer experience, documentation, support and pricing. It also covers hardware requirements, standards compliance, operating systems supported, and key modules for acquisition, cataloging, circulation, indexing and serials management. Important evaluation factors are speed, reliability, security, scalability, internationalization, portability and use of standards.
The document discusses SAP Business Workflow concepts including its purpose, terminology, advantages, and domains of application. The key purposes of SAP Business Workflow are to streamline business processes, ensure correct processes are followed, and formally define and implement processes. It provides benefits such as transparency, increased efficiency, and improved process control and monitoring.
DF2UFL 2012: Workflows: Making the MOST of Salesforce.com Native FunctionalityJennifer Phillips
DF2UFL 2012
Morning Session: Workflow - Making the MOST of Salesforce.com Native Functionality
Presented by: CloudTrigger [Silver Sponsor] Sean Wolfman
erpnext.com
On Demo Day, all team members present what they did in the month out of their own initiative. What features did they make or what documentation they wrote, or test cases, or a new product, or a new marketing initiative. It could be anything that adds value to ERPNext.
All the Demo Day presentations are made public on the erpnext blog.
This also means Open Sourcing our management. So look forward to our presentations at the end of the month and follow us to understand how this experiment is working out for us.
This document provides guidance on effectively communicating technical information to different audiences. It discusses documenting processes, systems and user manuals to create consistency, enable training and ensure compliance. It emphasizes standardizing templates and best practices. The document also explains how to customize communications by considering the audience, their needs and level of technical knowledge. It categorizes typical audience groups as co-workers, management, executives and users, and provides examples of what each would need to know to make decisions. The key message is to think about the audience and summarize information simply rather than using jargon or talking above their level in order to gain acceptance and approval for initiatives.
From selection to license negotiation through activation, libraries need the ability to track the electronic resource acquisition process and support uninterrupted workflow through multiple people and/or departments. Existing systems store fragments of information about a resource, but they don’t support management of the progress of each resource through the electronic resource acquisition maze. Stanford and Claremont have configured the JIRA and Footprints ticketing systems to address this fundamental need. Our systems facilitate efficient and complete activation of e-resources, and allow greater transparency in the acquisitions process throughout the organization. We will demonstrate the key features & functionality of our independently configured systems and invite discussion about these critical improvements to electronic resource management systems.
The document discusses using helpdesk or ticketing systems to track electronic resources acquisitions where ERMS systems failed. It describes how Stanford University Libraries and Claremont Colleges' Library implemented JIRA and eRATS in Footprints respectively to standardize their processes, define problems, and provide transparency into the status of electronic resource orders and activations. Both systems structure metadata, enable coordination between teams, and collect email trails to successfully track electronic resources acquisitions.
Quick start articles help you get set up sooner so you can begin performing the basic Business Central functions you need. The sections offer beginner's guides that help you get familiar with the features you need in Business Central. In each quick start, you'll find links to more advanced content about the functionality, should you need it. Get in Touch for Business Central Implementation: https://www.dynamicssquare.com.au/business-central-implementation/
Automate Evolve Training: Excel Workflow for Automatic RoutingPrecisely
Ready to route business processes to the right people at the right time, all while providing visibility into current and completed processes?
It’s achievable by adding a workflow to existing data templates – and that’s what we’ll cover during our Automate Evolve training on December 5, led by Tammy Lake, Senior Sales Engineer.
This session’s for you if you’re interested in taking your new or existing Excel data template to the next level. What does that look like? Adding a custom workflow that automatically routes your business processes for things like data collection, approvals, and running scripts.
You’ve already seen the value Studio scripts can bring to SAP data upload/download processes. Now, you can realize even more value by automating the manual before and after steps to complete your end-to-end business process automation.
This session will be filled with a variety of demos, including how to:
• add a workflow to an existing Excel template
• set up Excel templates to pass critical data to workflows
• set options for conditional routing and approvals
Through these demos, you’ll gain plenty of actionable takeaways that you can start implementing right away – including how to:
• interact with SAP from both business user and script developers’ perspectives
• interact with an Excel workflow from the Excel ribbon
• set different options for data validate and SAP posting, approvals, emails, and more
You’ll leave this session feeling ready and empowered to save time, boost efficiency, and change the way you work.
Automate Evolve reduces your dependency on technical resources to help create automation scenarios, remove the guesswork, and get complete visibility into business processes – and our team of experts is here to make sure you get the most out of our solution throughout the journey.
Questions? Tammy will be ready to answer them during a live Q&A at the end of the session
Project Management Tools for E-Discovery and Litigation Supportsclark22301
Two law firms shared their experiences designing and implementing project management tools for e-discovery and litigation support. Both firms started by identifying goals like tracking work, increasing visibility, and creating centralized knowledge bases. They selected web-based, customizable platforms like SharePoint that had low barriers to adoption. Their systems evolved from basic forms to track productions and data loads to more integrated workflows with alerts, reporting, and future integration plans. Key lessons included starting small to solve pressing problems and getting input from staff.
David Gage has over 10 years of experience in IT auditing and support roles. He is currently an IT Internal Auditor at Cisco Systems where he conducts quarterly audits of internal processes, identifies risks, and assists with remediation plans. Previously, he worked as a Senior IT Analyst and Systems Administrator at Cisco and Stiefel Laboratories, where he provided end-user support, managed systems imaging, and supported mobile devices. He has extensive experience with Windows, virtualization, security, networking, and hardware/software applications.
E-Business Suite Customization Impact Assessmenteprentise
The document discusses eprentise's ability to consolidate multiple Oracle E-Business Suite instances and change underlying structures without reimplementation. It outlines the challenges of customizations, how to identify customizations, and how to assess the impact of changes on customizations. The agenda includes introductions, discussing changes and challenges, defining customizations, customization assessment, configuration impact assessment, and a Q&A.
David Gage has over 15 years of experience in IT roles. He is currently an IT Internal Auditor at Cisco Systems where he conducts quarterly audits of internal processes to identify risks and assist in developing risk mitigation plans. Previously, he was a Senior IT Analyst at Cisco and Systems Administrator at Stiefel Laboratories where he supported over 700 and 430 users respectively and managed various systems and networks. He has a wide range of technical skills and experience across operating systems, virtualization, security, imaging, and more.
Alert Framework - Alert your organization to errors, changes, and stalled transactions. This webinar covers the Alerts Framework, which is a PeopleSoft Enterprise Component, enables you to alert your organization to errors, changes, and stalled transactions. It is a tool that is not limited to developers. If you can write a PeopleSoft Query, you can create an Alert. With alerts, you can scan PeopleSoft tables and receive alerts when exceptions are found. These alerts can include a link to the PeopleSoft page where you can review or correct the issue.
The document provides an agenda and overview for an End User Services training on new processes and tools being implemented. It includes sections on why changes are being made, an overview of new ITIL processes like incident and change management, new terminology, and tools like Clarify and Robohelp that are being introduced. The training aims to familiarize participants with the new ways of working and help with the transition to the new processes and systems.
This document discusses modules for inputting and retrieving data and documents. It notes that supplemental input processes like EDI and fax are also used. While input data may meet standards, retrieval metadata may not capture all necessary content. A sample is provided showing different types of documents and their metadata. The document recommends tasks to analyze current processes and integrity of repositories to improve metadata and integration between input and retrieval systems.
The document discusses the standard and non-standard implementations of Oracle's BI Publisher tool within Oracle EBS applications. It provides an overview of the standard data model, layout templates, report creation, and delivery methods. Examples are also given of variations seen in applications like Advanced Collections, Advanced Procurement, and Payables.
Similar to In with the new out with the old castro-wu-final-3-30-2012 (20)
Communicating effectively and consistently with students can help them feel at ease during their learning experience and provide the instructor with a communication trail to track the course's progress. This workshop will take you through constructing an engaging course container to facilitate effective communication.
Philippine Edukasyong Pantahanan at Pangkabuhayan (EPP) CurriculumMJDuyan
(𝐓𝐋𝐄 𝟏𝟎𝟎) (𝐋𝐞𝐬𝐬𝐨𝐧 𝟏)-𝐏𝐫𝐞𝐥𝐢𝐦𝐬
𝐃𝐢𝐬𝐜𝐮𝐬𝐬 𝐭𝐡𝐞 𝐄𝐏𝐏 𝐂𝐮𝐫𝐫𝐢𝐜𝐮𝐥𝐮𝐦 𝐢𝐧 𝐭𝐡𝐞 𝐏𝐡𝐢𝐥𝐢𝐩𝐩𝐢𝐧𝐞𝐬:
- Understand the goals and objectives of the Edukasyong Pantahanan at Pangkabuhayan (EPP) curriculum, recognizing its importance in fostering practical life skills and values among students. Students will also be able to identify the key components and subjects covered, such as agriculture, home economics, industrial arts, and information and communication technology.
𝐄𝐱𝐩𝐥𝐚𝐢𝐧 𝐭𝐡𝐞 𝐍𝐚𝐭𝐮𝐫𝐞 𝐚𝐧𝐝 𝐒𝐜𝐨𝐩𝐞 𝐨𝐟 𝐚𝐧 𝐄𝐧𝐭𝐫𝐞𝐩𝐫𝐞𝐧𝐞𝐮𝐫:
-Define entrepreneurship, distinguishing it from general business activities by emphasizing its focus on innovation, risk-taking, and value creation. Students will describe the characteristics and traits of successful entrepreneurs, including their roles and responsibilities, and discuss the broader economic and social impacts of entrepreneurial activities on both local and global scales.
Temple of Asclepius in Thrace. Excavation resultsKrassimira Luka
The temple and the sanctuary around were dedicated to Asklepios Zmidrenus. This name has been known since 1875 when an inscription dedicated to him was discovered in Rome. The inscription is dated in 227 AD and was left by soldiers originating from the city of Philippopolis (modern Plovdiv).
How to Setup Warehouse & Location in Odoo 17 InventoryCeline George
In this slide, we'll explore how to set up warehouses and locations in Odoo 17 Inventory. This will help us manage our stock effectively, track inventory levels, and streamline warehouse operations.
Beyond Degrees - Empowering the Workforce in the Context of Skills-First.pptxEduSkills OECD
Iván Bornacelly, Policy Analyst at the OECD Centre for Skills, OECD, presents at the webinar 'Tackling job market gaps with a skills-first approach' on 12 June 2024
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
How to Make a Field Mandatory in Odoo 17Celine George
In Odoo, making a field required can be done through both Python code and XML views. When you set the required attribute to True in Python code, it makes the field required across all views where it's used. Conversely, when you set the required attribute in XML views, it makes the field required only in the context of that particular view.
This document provides an overview of wound healing, its functions, stages, mechanisms, factors affecting it, and complications.
A wound is a break in the integrity of the skin or tissues, which may be associated with disruption of the structure and function.
Healing is the body’s response to injury in an attempt to restore normal structure and functions.
Healing can occur in two ways: Regeneration and Repair
There are 4 phases of wound healing: hemostasis, inflammation, proliferation, and remodeling. This document also describes the mechanism of wound healing. Factors that affect healing include infection, uncontrolled diabetes, poor nutrition, age, anemia, the presence of foreign bodies, etc.
Complications of wound healing like infection, hyperpigmentation of scar, contractures, and keloid formation.
In with the new out with the old castro-wu-final-3-30-2012
1. Jeannie Castro and Annie Wu
University of Houston Libraries
Electronic Resources and Libraries Conference, 2012
2. University of Houston
Libraries
Main library with 3
branches
160 staff members
2.2 million volumes
400,000 e-titles
Serve cliental of over
40,000
3. UH E-resources Management
Use Serials Solutions for almost all
ejournals and ebooks management
Individually subscribed ejournals used
to be cataloged in house, now
outsourced to Serials Solutions
4. Individual Ejournals Management
History
Utilize Help Desk Ticket for newly subscribed
ejournals
Add additional info for title(s) in ticket
Download and export OCLC records for the newly
subscribed title
Close Help Desk Ticket
5. Barriers for the Old Former Process
HelpDesk Ticket system is not designed for
ejournal management
Adding note for detailed ejournal data can be
cumbersome
Data about ejournals are not consistent or not
sufficient, thus confusing to catalogers
There was no way to track the process in lagging
subscriptions
There was no resource history of subscribed titles
6. Making the Change
Self-initiated team
Work out the new
workflow
Build the spread
sheet and set up
status in SS
Carry out the
designated work by
different units
8. Initiation of Individual E-journal
Process
Process begins with the Serials Review by
Acquisitions.
New e-journal titles are ordered based on SR
analysis.
ER staff take care of licenses if needed.
Individually subscribed titles go through the
designed workflow process
9. Old Workflow Process
HelpDesk Ticket sent to ER
by Acquisitions
ER verified the HelpDesk
Ticket info and forwarded it
to Cataloging
Cataloging cataloged the
new title and closed the
ticket
21. License Negotiation - Actions
Taken by ER
Request license from publisher
Mark up the license according to
University Policy
Negotiate the license
Create the Spreadsheet and update
the action log and summary note
Change status to Ready for Order in
SS
26. Ready for Order – Actions Taken
by Acquisitions
Create the order record
Verify that the information in the order
is correct
Pay the invoice
Change the status to ER Setup in SS
and the spreadsheet
32. ER Setup – Actions by ER
Input script into EZProxy
Verify access and test URL
Ensure that the coverage dates are
correct from the license
Change status to Coverage
Verification in SS and in spreadsheet
37. Coverage Verification – Action
Taken by Serials
Check several issues of the
subscribed journal to confirm the
access
Change status to Ready for
Cataloging – Individual eJournal in SS
and the spreadsheet
42. Ready for Cataloging – Action Taken by
Cataloging
Cataloging staff verify coverage
Changes the Serials Solutions record
to reflect correct dates and URL
Changes Status to Subscribed at
individual record level
46. Serials
Solutions
(status change)
Spreadshe
Outlook
et
(email alert)
(title info)
47. Challenges
Use of color
Work overlap
Tracking unsolved problems in
process
Communication among different
groups
48. Success Points
Shared process
Easy to integrate additional changes
in process
Transparency
Decent tracking of subscription
Collaboration
Process reusable for other formats
workflow
(collection size: 2.2 million volumes, 125 staff, 4 branches)Climate survey indicated people need more training for their job.
This presentation is about UH’s workflow. Let me give you a very brief synopsis of how the process begins. UH’s ACQ department does an annual serials review, which runs though November - the end of May. Around the middle of August, I’m give the finalized list of new serials titles to license or titles that are moving from print to either print + online or online only.I license all new titles if needed.The selection part of the workflow is the only part of the process that has remained the same between the old workflow and the new workflow
Old Workflow processAfter payment of new titles, helpdesk ticket sent to ER by ACQ Helpdesk ticket info verified by ER and forwarded on to cataloging. ER added some additional info to the ticketCataloging catalogs new title and closes the ticketThere were three departments involved with the process
This is a example of the usual helpdesk ticket sent by ACQ. Sometimes they had fewer titles, most of the time, they had quite a number more. It wasn’t uncommon to work with tickets that had about 40 titles on them.
ER would break the titles down and add the following information to each title,URLCoveragePrint ISSNDid ER add it to the proxy server?Tickets got unwieldy. It was very easy for titles to “fall of the ticket” and not get processed either because when ER worked on it, there was no access available or in the case of a platform change, the platform change had not yet occurred.Also, if you didn’t change the status of a ticket to “waiting on vendor” the ticket would escalate creating nasty alerts to the Helpdesk administrator. We didn’t find out until right before we had ceased using the helpdesk that we could halt the escalations.
New Process:There are 4 departments involved with the new process.During the selection process of the new ERM, Serials Solutions was specifically chosen because of the ability to utilize and create statuses. Early on, it was decided that a workflow could be developed using the statuses to push through new subscriptions.We use colour codes on spreadsheets to correspond to specific statuses that are created within Serial Solutions whose function is to send email alerts to notify staff in different departments that work is ready to be done on individual titles on a spreadsheetYellow - License Negotiation - Process Initiated by ER - Work completed by ERRed - Ready for Order - Process initiated by ER - Work completed by ACQOrange - ER Set - up - Process initiated by ACQ - Work completed by ERPurple - Coverage Verification - Process initiated by ER - Work completed by SerialsGreen - Ready for Cataloging - Process initiated by Serials - Work completed by catalogingWhite - Subscribed - Cataloging changes the final status to subscribed and the work for the specific title is completed
We use what Ssol has labeled the Database name, or what we refer to as the Collection level record, to entitle our spreadsheets which we keep on the library wide server. The directory where the spreadsheets are located has read/write privileges for everyone in Tech Services, and the share feature has been activated in the spreadsheets to allow mulitple people access to the spreadsheet at one time. Read only permissions have been give to the rest of the library. We wanted to give the selectors the opportunity to track their subscriptions, if they wanted to do so, thus increasing transparency between departments.In this example, we subscribed to a group of titles from the publisher Versita, which is hosted by MetaPress.
This is an example of the blank spreadsheet template we use with multiple tabsSummary TabPermanent accessProxy informationAny other information relevant to the publisher, for example, is the provider giving us “free” access to a few years of content for a specific period of time or rolling backfile informationAction LogWho has done what action in the spreadsheet on what date.Year tabsThe year the subscription beganFields: Title line number on the spreadsheet, Whether it is subscribed, coverage change, or not tracked, ISSN, Full Title, Year Range, URL, order number, Permanent access, proxied, Provider history (where we input platform change information), and any additional notes. The Permanent Access and Proxied columns are usually deleted since each collection level name usually corresponds to one specific license. But, for example, in the case of the collection level record called Single Journals, it contains journals from multiple publishers, so we need that information to be title specific.
The new workflow begins with ER creating a resource history note with the collection level record name and the publisher or provider in parentheses after it. We do this to distinguish which collection level record we are going to use. We input the location of the spreadsheet and spreadsheet name, attach the collection level record to the note and add a comment about which particular year’s serials review has added titles to the spreadsheet. We do this to preserve the institutional memory that disappears every time someone leaves employment or retires.
The first step in the workflow process is license negotiation. ERChanges the status to license negotiationEnsures that the 4 boxes in the Display In: section are unchecked. If we leave the boxes checked, it cues serials solutions to activate the title in 360 Core, 360 Link, send us the MARC records before we are ready for them, and input the titles into Summon.Ensures that the Title Coverage box that says “We only subscribe to some titles in this database” is checked. If we don’t check this box, the status is changed to License Negotiation for all titles in the collection level record
By changing the stats to license negotiation, it automatically sends an email alert though Outlook to select people in the library. Currently, an alert goes to Acquisitions to let them know action is forthcoming on this collection and to Collection Development so they are aware that new subscriptions are being processed
ER creates the spreadsheet, with the Title number (which is different from the line number in the spreadsheet), whether the title is a new subscription, coverage change, or if the title needs to be set to not tracked, Ssol’s terminology for deactivated in the system, the ISSN, the Full title, and the year range or coverage which is taken directly from the license.
The action log is updated with the date the action has taken place, the person who did the action, and a notation which is the year of the tab colon the title numbers that were worked on comma and the status the person doing the work set it to in serials solutions.In this example, on November 18, 2011, I worked on the 2012 tab in this spreadsheet on title numbers 1-6 and I set the status to license negotiation
Since I did the license, I input the permanent access into the summary tab. The summary tab contains all pertinent information from the license that relates to any work that ACQ or Cataloging may do. So, things like permanent access or rolling backfile information would be found on the summary tab.
In License negotiation, ER specificallyRequests the license from the publisher, marks it up according to University Policy, and negotiates the licenseCreates the spreadsheet with the new subscription information, updates the action log and summary tabsWhen finished with the work, ER hands it off to ACQ by changing the status to Ready for Order in Ssol
You can see here that the status has been changed to ready for order
The email alert which is sent by ER to ACQ specifically states that the collection level record, in this case Versita, has been changed for Ready for Order and that the title is ready for ACQ to work on it.
ER has changed the colours on the 2012 Tab in the spreadsheet to RED
ER has updated the action log that the status has been changed to Ready for order
Once ACQ receives the alert they Create the order record, if one needs to be createdVerify the info in the order record is correctPay the invoiceWhen finished with the work, ACQ hands it off to ER by changing the status to ER Setup in Ssol
You can see here that the status is changed to ER Setup.
The alert has been sent by ACQ to ER Staff alerting us that action needs to be taken on a specific spreadsheet
ACQ has changed the colour to orange and added the order numbers to the spreadsheet
Once ER receives the notification, we immediately either add a new Ezproxy script or verify that the existing proxy script is in synch with OCLC’s latest version and note it on the action log.
Once ER receives the alert, weInput or verify the Ezproxy scriptEnsure the URL worksVerifies that the coverage dates are correct from the licenseWhen finished with the work, ER hands it off to Serials by changing the status to Coverage Verification in Ssol
You can see here that the status has been set to CV
You can see the email alert which has been sent by ER to Serials notifying them that work needs to be done on titles in a spreadsheet
ER has changed the colour to purple. IF the URL is different than what is in Ssol, ER adds the corrected URL to the URL column. Serials staff use that URL when checking coverage.This is an important step in the university’s auditing process. It is viewed as similar to checking in an issue, where we are verifying what we pay for.
ER has added the status change to the Action log
Once Serials receives the alert, theyCheck the coverage to ensure we are getting what we are paying for.When finished with the work, Serials hands it off to Cataloging by changing the status to Ready for Cataloging in Ssol
You can see here where the status has been changed to ready for cataloging
Here is the alert sent by Serials to cataloging notifying them that work needs to be done on a spreadsheet
Serials has changed the colour coding to green
Serials has updated the action log with the status change
Once Cataloging receives the alert, theyReverify coverage to a deeper levelChange the dates and URL in Ssol if necessaryWhen finished with the work, Cataloging finishes the workflow process by changing the status to Subscribed in Ssol
As you can see in the subscribed record,All the boxes in the Display in: section are checked, making the title available in all of our Serials Solutions services, requesting MARC Updates, and making the title available in SummonIf custom dates were necessary, they would go into the Custom Coverage dates sectionIf a custom URL was necessary, it would be reflected in the Custom URL section
Allcolour has been removed from the spreadsheet
Cataloging staff have added the status change to the action log
It is a cyclical process, using 3 main systemsSerials SolutionsMicrosoft OutlookMicrosoft ExcelWhen a person finishes their work in the workflow, they change the status in Ssol, which generates an email alert to the next person responsible for continuing the workflow, who is then notified to take some action on the spreadsheet.I will turn it over to Annie to discuss the Challenges and our many success points.