A presentation by Matt Shreeve from curtis+cartwright Consulting Ltd..
Presented at the Preserving Software workshop, Brettenham House, London, 7 July 2010
Presentation by Steve Crouch, Software Architect at the Software Sustainability Institute.
Presented at the Digital Social Research: Sustainability Training Workshop at OeRC, Oxford on 12 December 2011.
This document discusses the prospects and challenges of developing an open source clinical trials data management system. It notes the increasing regulatory requirements for clinical trials data and how proprietary systems can be costly. It advocates for an open source approach using widely adopted open source software like PostgreSQL and Apache. The document describes OpenClinica, an existing open source clinical trials system, and one organization's experience piloting it in Africa. Challenges discussed include lack of technical expertise and resources to support customization and maintenance.
What researchers want with regard to research data management (RDM)heila1
Surveys, Surveys: Survey at UP 2010, Survey at UP 2013
Survey at CSIR 2013
RDM pilots @ UP
Started with one pilot; other researchers followed
What next?
This document discusses how open ecosystems can help science by storming the cloud. It argues that making data, software, and computing resources open through cloud-based platforms removes barriers and allows for more collaborative and interdisciplinary research at larger scales. This approach broadens participation in science and can accelerate progress by building on others' work.
This document discusses the benefits of open science over closed or proprietary approaches to data, software and publishing. It argues that open approaches remove barriers, allow for broader collaboration and participation, accelerate the progress of science, and avoid issues like redundant efforts, high costs and restrictions to access associated with closed models. Specific benefits mentioned include easier data sharing, reproducibility of results, more interdisciplinary research, and the development of better tools through an open and collaborative process.
Building Data Ecosystems for Accelerated Discoveryadamkraut
Large federated data ecosystems require diverse teams that can design, build, and integrate a broad range of services to support scientific workflows. Our collaborative team operates at the intersection of science, technology, and data to assess, implement, and teach the key capabilities and capacities modern healthcare and life science needs. Learn the data management techniques, tools, platforms, and frameworks that are proven to be effective at solving complex problems at scale.
The document discusses the creation of a wiki catalogue to catalog open source toolkits and testbeds related to software defined networking (SDN), network function virtualization (NFV), mobile edge computing (MEC) and 5G technologies. It notes that there are many toolkits and testbeds but a lack of visibility among researchers. A wiki is proposed to provide a centralized place for researchers, students and developers to discover relevant tools and testbeds. The wiki is being developed in phases, beginning with data collection and developing the initial structure, then opening it for community contributions and updates.
Curation-Friendly Tools for the Scientific Researcherbwestra
Presentation for Online Northwest Conference, in Corvallis Oregon, February 10, 2012.
Highlights electronic lab notebooks (ELN) and OMERO (Open Microscopy Environment) as two tools that enable researchers to better manage their research data.
Presentation by Steve Crouch, Software Architect at the Software Sustainability Institute.
Presented at the Digital Social Research: Sustainability Training Workshop at OeRC, Oxford on 12 December 2011.
This document discusses the prospects and challenges of developing an open source clinical trials data management system. It notes the increasing regulatory requirements for clinical trials data and how proprietary systems can be costly. It advocates for an open source approach using widely adopted open source software like PostgreSQL and Apache. The document describes OpenClinica, an existing open source clinical trials system, and one organization's experience piloting it in Africa. Challenges discussed include lack of technical expertise and resources to support customization and maintenance.
What researchers want with regard to research data management (RDM)heila1
Surveys, Surveys: Survey at UP 2010, Survey at UP 2013
Survey at CSIR 2013
RDM pilots @ UP
Started with one pilot; other researchers followed
What next?
This document discusses how open ecosystems can help science by storming the cloud. It argues that making data, software, and computing resources open through cloud-based platforms removes barriers and allows for more collaborative and interdisciplinary research at larger scales. This approach broadens participation in science and can accelerate progress by building on others' work.
This document discusses the benefits of open science over closed or proprietary approaches to data, software and publishing. It argues that open approaches remove barriers, allow for broader collaboration and participation, accelerate the progress of science, and avoid issues like redundant efforts, high costs and restrictions to access associated with closed models. Specific benefits mentioned include easier data sharing, reproducibility of results, more interdisciplinary research, and the development of better tools through an open and collaborative process.
Building Data Ecosystems for Accelerated Discoveryadamkraut
Large federated data ecosystems require diverse teams that can design, build, and integrate a broad range of services to support scientific workflows. Our collaborative team operates at the intersection of science, technology, and data to assess, implement, and teach the key capabilities and capacities modern healthcare and life science needs. Learn the data management techniques, tools, platforms, and frameworks that are proven to be effective at solving complex problems at scale.
The document discusses the creation of a wiki catalogue to catalog open source toolkits and testbeds related to software defined networking (SDN), network function virtualization (NFV), mobile edge computing (MEC) and 5G technologies. It notes that there are many toolkits and testbeds but a lack of visibility among researchers. A wiki is proposed to provide a centralized place for researchers, students and developers to discover relevant tools and testbeds. The wiki is being developed in phases, beginning with data collection and developing the initial structure, then opening it for community contributions and updates.
Curation-Friendly Tools for the Scientific Researcherbwestra
Presentation for Online Northwest Conference, in Corvallis Oregon, February 10, 2012.
Highlights electronic lab notebooks (ELN) and OMERO (Open Microscopy Environment) as two tools that enable researchers to better manage their research data.
The document discusses expanding support for software users by providing multiple avenues of help including email lists, FAQs, tutorials, a public issue tracker, and chat rooms. It emphasizes being honest about quality of service commitments like response times, supported platforms and issue scope, as well as types of support offered such as general help or tailored solutions. Alternative resources are suggested to help users help each other through a public archive and code drops while still ensuring individual requests are addressed.
The document discusses several key aspects of project governance, ownership, exploitation, and funding for software projects, including:
1) Governance models can range from a single leader to a meritocratic model, and the level of control needs to balance the originator's vision with expanding contribution.
2) Ownership is usually defined by copyright, but gets complicated with many contributors; contribution agreements and a single custodian can help define ownership and accountability.
3) Exploitation considers how the software can move forward commercially or as open source, targeting current and potential new users as well as integrators and partners.
4) Funding can come from grants, donations, services, licensing, or spin-
The document discusses code repositories and recommends hosting code online for open source projects. It describes how code repositories provide a safe place to store code, manage changes, and collaborate. It then discusses local versus internet repositories and recommends internet repositories for open source projects to avoid hosting burdens. Several popular online repositories are described, including SourceForge, Google Code, and GitHub.
The document discusses enabling smooth transitions between software maintainers. It suggests that when inducting a new maintainer, an experienced maintainer should discuss the software's design, develop code together, and walk through the code. For self-guided learning, documentation like user docs, tests, design docs and commented source code can help navigate understanding. When inheriting a large codebase, inspecting the code, documenting assumptions and designs, and writing tests and user docs creates resources to help future maintainers. Well structured code with tests that demonstrate functionality form a minimal effective handover.
This talk was presented by Simon Hettrick at the University of Southampton, Digital Economies Christmas Party.
The talk covered three activities of the Software Sustainability Institute: the Collaborations Workshop, the Agents network and Ask Steve!
Presentation by Steve Crouch, Software Architect at the Software Sustainability Institute.
Presented at the Digital Social Research: Sustainability Training Workshop at OeRC, Oxford on 12 December 2011.
A summary and all the slides for the lightning talks session at the 2013 Workshop for e-Infrastructure trainers event, which took place at the Hartree Centre, in Cheshire.
Introduction to the Software Sustainability Institute and a record of the discussion held at the JISC RI Software Sustainability Workshop on the 12th May 2010.
The introductory talk given by the Software Sustainability Institute's Simon Hettrick at the 2013 Workshop for e-Infrastructure trainers event, which took place at the Hartree Centre, in Cheshire.
The document provides information about a workshop hosted at www.software.ac.uk, including details on how it works, the events team members, ways to provide feedback, announcements, an agents network, and collaborative ideas activities. Attendees are encouraged to meet new people, visit the website for information, email (but not attach) documents, and that the workshop is flexible.
The document discusses the Software Sustainability Institute's community engagement efforts, including its Agents/Super Pals program and Fellows program. It recruits early-career and mid-career researchers to gather intelligence, run workshops, and provide feedback. The Fellows program has grown from 10 Agents in 2011 to 15 Fellows in 2013 across various research domains. The goals are to effectively serve the research community, maximize the Institute's impact, and promote awareness of software sustainability best practices.
Presented by Simon Hettrick at the e-Infrastructure Academic User Community Forum, this talk provides a number of recommendations for improving the provision of training for e-Infrastructure.
A presentation by Neil Chue Hong, Director of the Software Sustainability Institute.
Presented at the Preserving Software workshop, Brettenham House, London, 7 July 2010.
Issue tracking allows organizations to manage changes and bugs in an ordered way. An issue can represent any query, occurrence, or task that may impact a project, such as a software bug, request for change, or action item from a meeting. When an issue is reported, it goes through a typical workflow of being assigned, accepted, worked on, and eventually closed or reopened. Popular open source bug trackers include Bugzilla, Trac, and JIRA, with Trac being a good example of a lightweight yet powerful option that allows cross-referencing with wikis and version control systems.
This document provides guidance on carefully selecting open source software for adoption and long-term reuse. It emphasizes the importance of evaluating several key factors, such as whether the software meets functional requirements both currently and for the future, has an active user and developer community, provides good documentation and support, remains up to date and interoperable with standards, and has a development roadmap that indicates ongoing support. The document advises asking the developer community questions and provides an example of thoroughly evaluating the Taverna workflow system based on these criteria.
Cultivating Sustainable Software For ResearchNeil Chue Hong
Keynote given at the NSF Cyberinfrastructure Software and Sustainability Workshop, March 26th-27th 2009, Indianapolis.
Exploration of software sustainability based on experiences from UK.
Developing of a web-based application to facilitate patient treatment adheren...Gunther Eysenbach
This document summarizes the development of a web-based application to facilitate patient adherence to CPAP treatment for sleep apnea. A team including clinicians, psychologists, and software engineers planned to develop a motivational program using self-management strategies and interactive features. The application would track patient progress over time for use by patients and providers. The team's timeline involved initial planning, prototyping, implementation, testing, deployment, and evaluation over 12 months to create and study the feasibility of the adherence application.
Developing of a web-based application to facilitate patient treatment adheren...Gunther Eysenbach
This document summarizes the development of a web-based application to facilitate patient adherence to CPAP treatment for sleep apnea. A team including clinicians, psychologists, and software engineers conceptualized an interactive motivational program that tracks patient progress over time using self-reported surveys and motivational messages. The application was developed over 12 months, including prototyping user scenarios, designing interfaces, implementing features, and testing, with the goal of evaluating the application's impact on sleep quality, daytime sleepiness, quality of life, and adherence in future feasibility studies.
This document discusses software as a research object and the importance of research software. Some key points:
- Many researchers rely on software for their work but few have formal software training. Software is integral to modern research.
- Studies have found low reproducibility in scientific publications due to issues with unavailable software and code. Proper documentation and sharing of research software is needed.
- The Software Sustainability Institute aims to cultivate better, more sustainable research software to enable world-class research. They provide training, community support, and advocate for improved software practices and policies.
- Culture change is needed to incentivize sharing of research software and code. Mechanisms are emerging to properly credit software contributions and cite
The document discusses the advantages of implementing an electronic lab notebook (ELN) system, including improved productivity, efficiency, and information management. It also addresses the importance of integrating the ELN with other informatics solutions and examines whether a "paperless lab" is attainable. Key challenges include functionality, long-term data preservation, legal and regulatory considerations, and user adoption.
The document discusses the challenges of laboratory integration and outlines some potential solutions. It contrasts the electronic laboratory with the integrated laboratory. The objectives of laboratory integration include smoother workflows, less data entry, easier compliance, and improved efficiencies. However, barriers include a lack of data standards, communication standards, and a common language. Vendor collaboration, industry standards, and community action are suggested to help overcome these barriers and enable the evolution of data standards.
The document discusses expanding support for software users by providing multiple avenues of help including email lists, FAQs, tutorials, a public issue tracker, and chat rooms. It emphasizes being honest about quality of service commitments like response times, supported platforms and issue scope, as well as types of support offered such as general help or tailored solutions. Alternative resources are suggested to help users help each other through a public archive and code drops while still ensuring individual requests are addressed.
The document discusses several key aspects of project governance, ownership, exploitation, and funding for software projects, including:
1) Governance models can range from a single leader to a meritocratic model, and the level of control needs to balance the originator's vision with expanding contribution.
2) Ownership is usually defined by copyright, but gets complicated with many contributors; contribution agreements and a single custodian can help define ownership and accountability.
3) Exploitation considers how the software can move forward commercially or as open source, targeting current and potential new users as well as integrators and partners.
4) Funding can come from grants, donations, services, licensing, or spin-
The document discusses code repositories and recommends hosting code online for open source projects. It describes how code repositories provide a safe place to store code, manage changes, and collaborate. It then discusses local versus internet repositories and recommends internet repositories for open source projects to avoid hosting burdens. Several popular online repositories are described, including SourceForge, Google Code, and GitHub.
The document discusses enabling smooth transitions between software maintainers. It suggests that when inducting a new maintainer, an experienced maintainer should discuss the software's design, develop code together, and walk through the code. For self-guided learning, documentation like user docs, tests, design docs and commented source code can help navigate understanding. When inheriting a large codebase, inspecting the code, documenting assumptions and designs, and writing tests and user docs creates resources to help future maintainers. Well structured code with tests that demonstrate functionality form a minimal effective handover.
This talk was presented by Simon Hettrick at the University of Southampton, Digital Economies Christmas Party.
The talk covered three activities of the Software Sustainability Institute: the Collaborations Workshop, the Agents network and Ask Steve!
Presentation by Steve Crouch, Software Architect at the Software Sustainability Institute.
Presented at the Digital Social Research: Sustainability Training Workshop at OeRC, Oxford on 12 December 2011.
A summary and all the slides for the lightning talks session at the 2013 Workshop for e-Infrastructure trainers event, which took place at the Hartree Centre, in Cheshire.
Introduction to the Software Sustainability Institute and a record of the discussion held at the JISC RI Software Sustainability Workshop on the 12th May 2010.
The introductory talk given by the Software Sustainability Institute's Simon Hettrick at the 2013 Workshop for e-Infrastructure trainers event, which took place at the Hartree Centre, in Cheshire.
The document provides information about a workshop hosted at www.software.ac.uk, including details on how it works, the events team members, ways to provide feedback, announcements, an agents network, and collaborative ideas activities. Attendees are encouraged to meet new people, visit the website for information, email (but not attach) documents, and that the workshop is flexible.
The document discusses the Software Sustainability Institute's community engagement efforts, including its Agents/Super Pals program and Fellows program. It recruits early-career and mid-career researchers to gather intelligence, run workshops, and provide feedback. The Fellows program has grown from 10 Agents in 2011 to 15 Fellows in 2013 across various research domains. The goals are to effectively serve the research community, maximize the Institute's impact, and promote awareness of software sustainability best practices.
Presented by Simon Hettrick at the e-Infrastructure Academic User Community Forum, this talk provides a number of recommendations for improving the provision of training for e-Infrastructure.
A presentation by Neil Chue Hong, Director of the Software Sustainability Institute.
Presented at the Preserving Software workshop, Brettenham House, London, 7 July 2010.
Issue tracking allows organizations to manage changes and bugs in an ordered way. An issue can represent any query, occurrence, or task that may impact a project, such as a software bug, request for change, or action item from a meeting. When an issue is reported, it goes through a typical workflow of being assigned, accepted, worked on, and eventually closed or reopened. Popular open source bug trackers include Bugzilla, Trac, and JIRA, with Trac being a good example of a lightweight yet powerful option that allows cross-referencing with wikis and version control systems.
This document provides guidance on carefully selecting open source software for adoption and long-term reuse. It emphasizes the importance of evaluating several key factors, such as whether the software meets functional requirements both currently and for the future, has an active user and developer community, provides good documentation and support, remains up to date and interoperable with standards, and has a development roadmap that indicates ongoing support. The document advises asking the developer community questions and provides an example of thoroughly evaluating the Taverna workflow system based on these criteria.
Cultivating Sustainable Software For ResearchNeil Chue Hong
Keynote given at the NSF Cyberinfrastructure Software and Sustainability Workshop, March 26th-27th 2009, Indianapolis.
Exploration of software sustainability based on experiences from UK.
Developing of a web-based application to facilitate patient treatment adheren...Gunther Eysenbach
This document summarizes the development of a web-based application to facilitate patient adherence to CPAP treatment for sleep apnea. A team including clinicians, psychologists, and software engineers planned to develop a motivational program using self-management strategies and interactive features. The application would track patient progress over time for use by patients and providers. The team's timeline involved initial planning, prototyping, implementation, testing, deployment, and evaluation over 12 months to create and study the feasibility of the adherence application.
Developing of a web-based application to facilitate patient treatment adheren...Gunther Eysenbach
This document summarizes the development of a web-based application to facilitate patient adherence to CPAP treatment for sleep apnea. A team including clinicians, psychologists, and software engineers conceptualized an interactive motivational program that tracks patient progress over time using self-reported surveys and motivational messages. The application was developed over 12 months, including prototyping user scenarios, designing interfaces, implementing features, and testing, with the goal of evaluating the application's impact on sleep quality, daytime sleepiness, quality of life, and adherence in future feasibility studies.
This document discusses software as a research object and the importance of research software. Some key points:
- Many researchers rely on software for their work but few have formal software training. Software is integral to modern research.
- Studies have found low reproducibility in scientific publications due to issues with unavailable software and code. Proper documentation and sharing of research software is needed.
- The Software Sustainability Institute aims to cultivate better, more sustainable research software to enable world-class research. They provide training, community support, and advocate for improved software practices and policies.
- Culture change is needed to incentivize sharing of research software and code. Mechanisms are emerging to properly credit software contributions and cite
The document discusses the advantages of implementing an electronic lab notebook (ELN) system, including improved productivity, efficiency, and information management. It also addresses the importance of integrating the ELN with other informatics solutions and examines whether a "paperless lab" is attainable. Key challenges include functionality, long-term data preservation, legal and regulatory considerations, and user adoption.
The document discusses the challenges of laboratory integration and outlines some potential solutions. It contrasts the electronic laboratory with the integrated laboratory. The objectives of laboratory integration include smoother workflows, less data entry, easier compliance, and improved efficiencies. However, barriers include a lack of data standards, communication standards, and a common language. Vendor collaboration, industry standards, and community action are suggested to help overcome these barriers and enable the evolution of data standards.
The Challenges Of, And Advantages In, Establishing A Consistent Architectural...Tim Eyres
Describes the challenges and benefits of having a consistent enterprise architecture framework within a global pharma research organization with examples from different industries.
Cat Herding and Community Gardens: Practical e-Science Project ManagementNeil Chue Hong
A talk given by Neil Chue Hong at the e-Science Project Management Symposium looking at issues and models of managing projects which are cross-organisation, cross-discipline and cross-usertype, based on experience of managing several e-Science projects.
Better software, better service, better research: The Software Sustainabilit...Carole Goble
Ever spotted some great looking software only to discover you can’t get it, it doesn’t work, there is no documentation to help fix it and the developers don’t have the time or incentive to help? Ever produced some software that you want to be widely used or have folks contribute? What’s the sustainability of that key platform/library/tool /database your lab uses day in and day out? Are you helping the providers? The same issues stand for Data (or as we now say “FAIR” Findable, Accessible, Interoperable, Reusable Data) and its metadata. Is anyone looking out for Europe’s data services– the datasets and analysis systems you use and you make – the standards they use and the curators and developers who make them? Or is FAIR just a FAIRy story? I’ll tell how two organisations with quite different structures and approaches - the UK’s Software Sustainability Institute and the ELIXIR European Research Infrastructure for Life Science Data – are working for the common goal of better software, better service, and better research.
https://www.rothamsted.ac.uk/events/14th-international-symposium-integrative-bioinformatics
Aspects of the sustainability of softwarePaul Walk
Sustainability in software development refers to both the preservation of software over time and the ongoing provision of software as a service. There are two main approaches to sustainable software: 1) Bundle software and dependencies together into a single deployable package. 2) Abstract important algorithms and store as documentation, while abandoning other parts. Sustainable development requires better engineering practices through training and support from the beginning of the development process. The sustainability of software must be addressed at the outset.
The document describes the first phase of developing the OnScience portal, which involved designing the architecture and schematics. Key points:
- The team split into groups based on skills to work on different phases. Phase 1 focused on architecture.
- Modules like a researcher rating system were planned to make the portal more useful than existing sites. The rating system considered factors like publications.
- Developing a robust e-commerce platform was a challenge to balance user and business interests.
- A dummy platform tested the rating system algorithm by having users create profiles before the public launch.
- The main page layout was designed using interface tools to optimize the user experience. PHP and JavaScript were selected for the technical
The Software Sustainability Institute (SSI) provides services to help research groups sustain their software over the long term. It collaborates with groups in various fields to improve key software through advice, training, and partnerships. Case studies describe projects in fields like fusion energy, climate modeling, geospatial data, and computational chemistry. The SSI aims to promote best practices and change perceptions so software is recognized as a valuable long-term asset, not just for initial research. Sustaining software requires support for both technical aspects and community engagement over decades.
Webinar - Design Thinking for Platform EngineeringOpenCredo
This document discusses approaching platform engineering with a design thinking mindset. It begins by outlining challenges with existing approaches, such as tools being difficult to use and responsibilities being blurred. It then defines platform engineering and describes design thinking, which integrates user needs, technology possibilities, and business requirements. The design thinking process involves empathizing with users to gain insights, defining opportunities, ideating solutions, prototyping ideas, and testing assumptions. The document argues that applying a human-centered design thinking approach helps focus on outcomes rather than just technology, surfaces conflicts, identifies new opportunities, and involves frequent testing with users. It concludes by recommending getting started with design thinking for platform engineering by identifying and prioritizing problems, engaging stakeholders
This document discusses various anti-patterns related to software development, architecture, and project management. It describes anti-patterns like stovepipe systems, vendor lock-in, and warm bodies. For each anti-pattern, it outlines typical symptoms, causes, exceptions, and potential solutions. The document also provides examples of anti-patterns like architecture by implication, design by committee, and reinventing the wheel.
Six Principles of Software Design to Empower ScientistsDavid De Roure
Keynote talk for Workshop on Managing for Usability:
Challenges and Opportunities for E-Science Project Management, 10-11 April 2008,
OeRC, University of Oxford, UK
Keynote on software sustainability given at the 2nd Annual Netherlands eScience Symposium, November 2014.
Based on the article
Carole Goble ,
Better Software, Better Research
Issue No.05 - Sept.-Oct. (2014 vol.18)
pp: 4-8
IEEE Computer Society
http://www.computer.org/csdl/mags/ic/2014/05/mic2014050004.pdf
http://doi.ieeecomputersociety.org/10.1109/MIC.2014.88
http://www.software.ac.uk/resources/publications/better-software-better-research
Open Source Web Content Management StrategiesKStod
DotNetNuke Co-Founder Shaun Walker shares "Effective Strategies for Evaluating and Eeploying Open Source Content Management Tools" at the Gilbane Conference 2010 in San Francisco
Similar to Preserving software workshop - Community engagement workshop (20)
Introduction from Neil Chue Hong, Director of the Software Sustainability Institute for session on "Publishing Research Data: What’s in it for me?" at Science, Policy, Outreach and Tools Online.
These are the combined slides from the lightning talks sessions at the Collaborations Workshop 2012. For speaker information, see: http://www.software.ac.uk/cw12/cw12-topics-lightning-talks
The document provides instructions for conducting breakout sessions, which include choosing a Chair and Scribe in the first 5 minutes to lead discussion on lessons learned, problems and solutions, further work needed, and resources. In the last 10 minutes, the Scribe distills the group's notes using a template, and the group chooses a presenter to report the results to the larger group via email.
Planning is essential for any project that produces software, even if it is research-oriented. Development plans should be detailed enough to provide guidance but not constrain the project. The plan should be useful to the project team and use tools that work best for the individuals involved. The plan should set regular milestones to release work in progress and review progress without locking in scope too early. A product-based approach to planning breaks work down into components that can be estimated, and the plan should include testing, integration, documentation, and release tasks.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Classic preservation : ‘putting in aspic’ where the software lies dormant once or more, and the benefit of preservation comes in the future
Living or active preservation : ‘cultivation’ where software continues to be developed, and the benefit of preservation comes mainly now
Liberating data
http://www.entrepreneur.com/tradejournals/article/64715526.html needs include long-term, secure, managed storage of identified, business-critical records new drug products may take 10 years or longer to develop Products are subject to rigorous inspection by national regulatory bodies – safety and effectiveness of drug Records and data that support a marketed drug's development must be available for regulatory inspection during the compound's lifetime, Compound lifetime generally assumed to be 40 years or longer long-term preservation plans include migration of source software versions, migrating records to appropriate data standards, and purchasing "virtual" computers to run obsolete software via emulation protocols.