The document provides an overview of Drupal for content creators. It discusses what Drupal is and how it can be used to build various types of websites. It covers basic Drupal terminology like nodes, menus, blocks, modules, and taxonomy. It also provides examples of setting up a simple homepage and menu structure for a new Drupal site.
This document discusses librarians developing websites to better provide information access. It notes that traditional libraries are moving online, where many users now access information. The document considers why librarians are well-suited for web development given their expertise in information access. It also evaluates different technologies for libraries to use, from online catalogs and social media to website builders and content management systems. Key criteria for choosing a technology include costs, complexity of the site, who will maintain it, and how it will be hosted. The document encourages librarians to explore options and extend their online presence to better serve library users.
Context and Linearity: Representing Structure in WikisJani Patokallio
Moving wikis beyond a bunch of unsorted pages: how can books, taxonomies and other structured and/or ordered content be represented in, edited in, and exported from MediaWiki? From Lonely Planet.
This document discusses consuming UW web services data in Drupal. It introduces the UW People, UW GWS Auth, and UW Courses modules, which pull data from the UW People and Course web services using a custom Locally Trusted Service (LTS) plugin model. The LTS manages API keys and certificates securely and provides the data to Drupal, which then stores it as nodes for easy querying, filtering, and display with Views and other features.
Drupal is a free and open source content management system (CMS) that can be used to build various types of websites and applications. External Services at the European Bioinformatics Institute uses Drupal to manage 33 portals, 23 EU project sites, and 10 internal EBI sites. Drupal provides tools for content authors to create, edit, and manage content through a web interface, and also gives developers flexibility to customize sites through modules, themes, and code. ES supports use of Drupal through virtual machines, version control, and development resources.
BASPUG May 2014 - Taming Your Taxonomy in SharePointJonathan Ralton
This document provides an agenda and overview for a presentation on taming taxonomies in SharePoint. The presentation covers content architecture and taxonomy concepts, metadata such as content types and site columns, and best practices for implementing metadata in SharePoint. It discusses defining the appropriate scope and hierarchy for content types and columns. The goal is to help attendees understand how metadata supports findability and usability of content in SharePoint.
Baltimore SharePoint Users Group - Worst Practices and Administrative BlundersDan Usher
The document appears to be a presentation about various technical, business, and social challenges related to SharePoint development and administration. It includes topics such as coding practices, infrastructure processes, permissions management, testing workflows, analytics tuning, certificate configuration, managed paths, audit log trimming, and service account management. The presenters are identified as Scott Hoag and Dan Usher.
Design a SharePoint Program for Ongoing Operational ExcellenceErica Toelle
This document outlines how to design a SharePoint program for ongoing operational excellence. It discusses establishing a program to manage SharePoint projects, including collecting business cases, prioritizing projects, establishing a project management methodology, and creating a center of excellence for reusing solutions. It provides a case study example of a company that saw cost savings, on-time project delivery, and increased user adoption by implementing such a SharePoint program.
The document provides an overview of Drupal for content creators. It discusses what Drupal is and how it can be used to build various types of websites. It covers basic Drupal terminology like nodes, menus, blocks, modules, and taxonomy. It also provides examples of setting up a simple homepage and menu structure for a new Drupal site.
This document discusses librarians developing websites to better provide information access. It notes that traditional libraries are moving online, where many users now access information. The document considers why librarians are well-suited for web development given their expertise in information access. It also evaluates different technologies for libraries to use, from online catalogs and social media to website builders and content management systems. Key criteria for choosing a technology include costs, complexity of the site, who will maintain it, and how it will be hosted. The document encourages librarians to explore options and extend their online presence to better serve library users.
Context and Linearity: Representing Structure in WikisJani Patokallio
Moving wikis beyond a bunch of unsorted pages: how can books, taxonomies and other structured and/or ordered content be represented in, edited in, and exported from MediaWiki? From Lonely Planet.
This document discusses consuming UW web services data in Drupal. It introduces the UW People, UW GWS Auth, and UW Courses modules, which pull data from the UW People and Course web services using a custom Locally Trusted Service (LTS) plugin model. The LTS manages API keys and certificates securely and provides the data to Drupal, which then stores it as nodes for easy querying, filtering, and display with Views and other features.
Drupal is a free and open source content management system (CMS) that can be used to build various types of websites and applications. External Services at the European Bioinformatics Institute uses Drupal to manage 33 portals, 23 EU project sites, and 10 internal EBI sites. Drupal provides tools for content authors to create, edit, and manage content through a web interface, and also gives developers flexibility to customize sites through modules, themes, and code. ES supports use of Drupal through virtual machines, version control, and development resources.
BASPUG May 2014 - Taming Your Taxonomy in SharePointJonathan Ralton
This document provides an agenda and overview for a presentation on taming taxonomies in SharePoint. The presentation covers content architecture and taxonomy concepts, metadata such as content types and site columns, and best practices for implementing metadata in SharePoint. It discusses defining the appropriate scope and hierarchy for content types and columns. The goal is to help attendees understand how metadata supports findability and usability of content in SharePoint.
Baltimore SharePoint Users Group - Worst Practices and Administrative BlundersDan Usher
The document appears to be a presentation about various technical, business, and social challenges related to SharePoint development and administration. It includes topics such as coding practices, infrastructure processes, permissions management, testing workflows, analytics tuning, certificate configuration, managed paths, audit log trimming, and service account management. The presenters are identified as Scott Hoag and Dan Usher.
Design a SharePoint Program for Ongoing Operational ExcellenceErica Toelle
This document outlines how to design a SharePoint program for ongoing operational excellence. It discusses establishing a program to manage SharePoint projects, including collecting business cases, prioritizing projects, establishing a project management methodology, and creating a center of excellence for reusing solutions. It provides a case study example of a company that saw cost savings, on-time project delivery, and increased user adoption by implementing such a SharePoint program.
Movin on Up - ScarePoint Friday Cincinnati 2016Jim Adcock
Cincinnati's version of SharePoint Saturday, on a Friday before Halloween
Our SharePoint environment is a lot like many others – a SharePoint 2007 implementation that was used more as a file dump than a collaboration space. With minimal user adoption, we were never quite ready to implement 2010, with a pilot SharePoint 2010 implementation stalled out of the gate.
In the meantime, some content was put on Box and other services to address external collaboration needs. Business users needed more relevant search results, content databases had grown uncomfortably large, and access controls had become spaghetti. Fortunately, site sprawl wasn’t too bad… except that the reason for that was the low adoption.
SharePoint 2013 arrived to a perfect storm – business and technology needs to be addressed, content that needs to be brought back in-house, and user adoption that needs to be improved. Time to upgrade!
See how we approached the upgrade, the issues than needed to be addressed, and the questions that needed to be answered.
This document discusses best practices for managing a large SharePoint environment based on the experience of Matt Linxwiler at ALSAC/St. Jude Children's Research Hospital. Some key practices include limiting site owner permissions to prevent sprawl, regularly cleaning up unused content and sites, avoiding custom code when possible, providing training to empower users, hiring dedicated SharePoint staff, and taking an iterative approach to deliver small usable portions of solutions over time. The goal is to ease the growing pains of a large SharePoint deployment through focus, the right people, and governance practices.
The meeting introduced SharePoint and discussed its benefits over traditional email for collaboration and knowledge management. Attendees learned how SharePoint allows documents to be stored and edited in one central place rather than accumulating copies through email exchanges. The group discussed setting up a pilot implementation of SharePoint sites for various schools and departments to improve workflows and information sharing. Objectives for staff included learning to use the main SharePoint features and determining what knowledge assets should be shared across the whole organization versus within individual units.
SPSNYC17 - The Wall: Overcoming SharePoint’s Site Collection BoundaryJonathan Ralton
This document describes a presentation on overcoming SharePoint's site collection boundaries. The presentation discusses defining the problem of maintaining consistency across site collections and discusses solutions for site lifecycles, taxonomy, workflows, and navigation that involve tools like PowerShell, content type publishing, and managed metadata. It provides demonstrations of using these techniques and tools to help manage content and processes across multiple site collections.
This document provides a status report on the State Library's project to upgrade its website from a FrontPage-based system to one using the open source content management framework Drupal. It discusses the library's needs for a website that is easier for users, presents it as a cohesive organization, and leverages collaboration. It outlines the challenges of the current system and how Drupal can help by allowing for improved information architecture, easier content creation and updating, and a platform that can adapt to changing technologies. The report notes that while consultants were originally planned to assist, the library is now building out the Drupal environment itself, undergoing training, testing modules, and planning next steps to move content over from the existing site.
Your Road to Modern Communication SitesD'arce Hess
This document provides a summary of modern communication sites in Office 365 and how to migrate to them. It discusses the evolution of communication and collaboration technologies over time from early SharePoint versions to modern sites. It introduces communication sites and their capabilities, including out-of-the-box web parts, customization options like themes, and using the SharePoint Framework. It emphasizes the importance of change management, training, and governance when migrating to ensure a successful transition.
IWMW 2002: Portals and CMS:" Why You Need Them BothIWMW
Plenary talk on “Portals and CMS:" Why You Need Them Both” given by Paul Browning at the IWMW 2002 event.
See http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2002/sessions.html#talk-browning
How many times have you had this discussion? Business: "What can SharePoint do?" You: "What do you want to do?" Business: "I can't tell you what I want to do until I know what it can do?"
In this session we will walk through the presentation used at the City of Minneapolis to turn this conversation upside down. At the end of this session you will have the tools to turn the focus to what the business needs instead of what SharePoint can do.
SharePoint Engage Phoenix 2017
Our SharePoint environment is a lot like many others – a SharePoint 2007 implementation that was used more as a file dump than a collaboration space. With minimal user adoption, we were never quite ready to implement 2010, with a pilot SharePoint 2010 implementation stalled out of the gate.
In the meantime, some content was put on Box and other services to address external collaboration needs. Business users needed more relevant search results, content databases had grown uncomfortably large, and access controls had become spaghetti. Fortunately, site sprawl wasn’t too bad… except that the reason for that was the low adoption.
SharePoint 2013 arrived to a perfect storm – business and technology needs to be addressed, content that needs to be brought back in-house, and user adoption that needs to be improved. Time to upgrade!
See how we approached the upgrade, the issues than needed to be addressed, and the questions that needed to be answered.
Lessons Learned in the Development of a Web-scale Search Engine: Nutch2 and b...Chris Mattmann
This document summarizes the history and development of the Nutch web search engine project. It discusses how Nutch evolved from its original version to incorporate Hadoop and become more modular by delegating functions like indexing and parsing to other Apache projects like Solr and Tika. The current version, Nutch 2.0, aims to have a slimmed down architecture where it acts as a delegator to these other frameworks rather than handling these functions itself. The document also reflects on lessons learned from earlier stages of the project around community engagement, maintenance, and configuration challenges.
Tips for a successful SharePoint Migration strategyDon Daubert
This document provides tips for a successful SharePoint migration strategy. It discusses various migration options such as in-place upgrades, database attach methods, and third-party migration tools. It emphasizes the importance of discovery and planning, including inventorying the current farm configuration and content. The document also covers implementation, testing the migration plan, and potential issues to watch out for such as metadata not transferring accurately. Post-migration steps are also highlighted like validating content and functionality transferred correctly.
Roles are necessary for successful SharePoint implementations and evolve over time. Initially, core roles include the executive champion to provide buy-in, the platform owner to oversee priorities, and an IT pro to manage servers. As implementations mature, additional roles emerge like developers for customizations, business analysts to understand needs, and site collection administrators to decentralize responsibilities. Scenarios like an intranet require roles like designers for branding, and governance committees to determine policies.
Thinking big with SharePoint the Howard Hughes Way!Vibha Godse Gore
The document summarizes how Howard Hughes Corporation implemented a large SharePoint platform to solve business problems. They migrated over 10 TB of content from file shares and systems into SharePoint sites and libraries. They also automated key business processes using workflows and forms. Challenges included a large content volume, integrating with line of business apps, and adopting users. Now they are planning a migration to Office 365 to leverage modern features while addressing migration of on-prem components like Nintex workflows.
This document provides an overview of SharePoint features and the SharePoint development paradigm. It discusses:
1) The history of SharePoint from 1999 to the present, including versions like SharePoint Server 2001, 2003, 2007, 2010, 2013, and Office 365.
2) Key SharePoint features like social capabilities, document handling, search, business intelligence, mobile access, customization options, and enterprise content management.
3) The SharePoint hierarchy including server farms, web applications, site collections, sites, and lists/libraries.
4) SharePoint development units like site columns, content types, lists, libraries, and pages. Development types including browser, designer, and Visual Studio customization.
This document provides a summary of modern communication sites and customization capabilities. It begins with an overview of where communication sites have evolved from older SharePoint versions. It then discusses how to create communication sites and the out-of-box web parts. Customization options are explained like themes, extensions, and using the SharePoint Framework (SPFx) to build custom web parts. The importance of change management and communication for migrations is stressed. Upcoming features like hub sites and a roadmap for site owners are also mentioned.
SharePoint Saturday Richmond - So you want to implement SharePoint 2010, what...eavanesian
This document provides an overview of factors to consider before implementing SharePoint in an organization. It discusses questions to answer such as having a clear vision, defining critical terms, establishing governance, and developing a communication plan. It also covers assessing organizational readiness through examining support staff, available funding, company culture, and user requirements. Finally, it addresses assessing IT staff availability and ensuring the necessary skills are present, such as network administration, system administration, database administration, and SharePoint development expertise. The key takeaways are that SharePoint implementation requires a paradigm shift and cannot be treated like a typical IT project.
Does your website have a ton of data? How do your users find the relevant pages among all the noise in your site?
Solr can help deliver the pertinent search results to your users regardless of your site's size.
Apache Solr is a Java program that integrates with the Drupal contrib module that allows your users to quickly search millions of records and narrow down the results with minimal system impact.
Redesigning a Website Using Information Architecture PrincipalsJenny Emanuel
This document provides an overview of information architecture concepts for redesigning a library website. It discusses key frameworks like accessibility, usability and balancing context, content and users. The importance of understanding the website context, users, tasks, content and politics is emphasized. Structuring content into areas like information, resources and services is suggested. The document also outlines the agenda, which focuses on frameworks, structuring, organizing, labeling and redesigning a website.
-DSpace Under the Hood-
As presented at OR10 in July 2010-
Part 1: How does DSpace work?: Whilst you don't need to be a mechanic to drive a car, it is helpful if you have a basic understanding of how a car works, what bits do different jobs, and how to top up your oil and pump up your tyres / tires. This presentation will give an overview of the DSpace architecture, and will give you enough knowledge to understand how DSpace works. By knowing this, you will also learn about ways DSpace could be used, and ways in which it can't be used.
Part 2: The development process and YOUR role in it:
DSpace development in undertaken by the DSpace community. No one, or no organisation is in charge, and without contributions from the DSpace community the platform would not continue to develop and evolve. Sometimes it can appear that there are people in charge, or that unless you are a technical developer then there is no way or need to contribute. This presentation will explain how DSpace development usually takes place, where and who has input at different stages, and will equip you to contribute further, or to help you contribute for the first time.
Presenters - members of the DSpace Committers and DSpace Global Outreach Committee:
Lewis, Stuart ; Hayes, Leonie ; Stangeland, Elin ; Shepherd, Kim ; Jones, Richard ; Roos, Monica
"Scaling RAG Applications to serve millions of users", Kevin GoedeckeFwdays
How we managed to grow and scale a RAG application from zero to thousands of users in 7 months. Lessons from technical challenges around managing high load for LLMs, RAGs and Vector databases.
Movin on Up - ScarePoint Friday Cincinnati 2016Jim Adcock
Cincinnati's version of SharePoint Saturday, on a Friday before Halloween
Our SharePoint environment is a lot like many others – a SharePoint 2007 implementation that was used more as a file dump than a collaboration space. With minimal user adoption, we were never quite ready to implement 2010, with a pilot SharePoint 2010 implementation stalled out of the gate.
In the meantime, some content was put on Box and other services to address external collaboration needs. Business users needed more relevant search results, content databases had grown uncomfortably large, and access controls had become spaghetti. Fortunately, site sprawl wasn’t too bad… except that the reason for that was the low adoption.
SharePoint 2013 arrived to a perfect storm – business and technology needs to be addressed, content that needs to be brought back in-house, and user adoption that needs to be improved. Time to upgrade!
See how we approached the upgrade, the issues than needed to be addressed, and the questions that needed to be answered.
This document discusses best practices for managing a large SharePoint environment based on the experience of Matt Linxwiler at ALSAC/St. Jude Children's Research Hospital. Some key practices include limiting site owner permissions to prevent sprawl, regularly cleaning up unused content and sites, avoiding custom code when possible, providing training to empower users, hiring dedicated SharePoint staff, and taking an iterative approach to deliver small usable portions of solutions over time. The goal is to ease the growing pains of a large SharePoint deployment through focus, the right people, and governance practices.
The meeting introduced SharePoint and discussed its benefits over traditional email for collaboration and knowledge management. Attendees learned how SharePoint allows documents to be stored and edited in one central place rather than accumulating copies through email exchanges. The group discussed setting up a pilot implementation of SharePoint sites for various schools and departments to improve workflows and information sharing. Objectives for staff included learning to use the main SharePoint features and determining what knowledge assets should be shared across the whole organization versus within individual units.
SPSNYC17 - The Wall: Overcoming SharePoint’s Site Collection BoundaryJonathan Ralton
This document describes a presentation on overcoming SharePoint's site collection boundaries. The presentation discusses defining the problem of maintaining consistency across site collections and discusses solutions for site lifecycles, taxonomy, workflows, and navigation that involve tools like PowerShell, content type publishing, and managed metadata. It provides demonstrations of using these techniques and tools to help manage content and processes across multiple site collections.
This document provides a status report on the State Library's project to upgrade its website from a FrontPage-based system to one using the open source content management framework Drupal. It discusses the library's needs for a website that is easier for users, presents it as a cohesive organization, and leverages collaboration. It outlines the challenges of the current system and how Drupal can help by allowing for improved information architecture, easier content creation and updating, and a platform that can adapt to changing technologies. The report notes that while consultants were originally planned to assist, the library is now building out the Drupal environment itself, undergoing training, testing modules, and planning next steps to move content over from the existing site.
Your Road to Modern Communication SitesD'arce Hess
This document provides a summary of modern communication sites in Office 365 and how to migrate to them. It discusses the evolution of communication and collaboration technologies over time from early SharePoint versions to modern sites. It introduces communication sites and their capabilities, including out-of-the-box web parts, customization options like themes, and using the SharePoint Framework. It emphasizes the importance of change management, training, and governance when migrating to ensure a successful transition.
IWMW 2002: Portals and CMS:" Why You Need Them BothIWMW
Plenary talk on “Portals and CMS:" Why You Need Them Both” given by Paul Browning at the IWMW 2002 event.
See http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2002/sessions.html#talk-browning
How many times have you had this discussion? Business: "What can SharePoint do?" You: "What do you want to do?" Business: "I can't tell you what I want to do until I know what it can do?"
In this session we will walk through the presentation used at the City of Minneapolis to turn this conversation upside down. At the end of this session you will have the tools to turn the focus to what the business needs instead of what SharePoint can do.
SharePoint Engage Phoenix 2017
Our SharePoint environment is a lot like many others – a SharePoint 2007 implementation that was used more as a file dump than a collaboration space. With minimal user adoption, we were never quite ready to implement 2010, with a pilot SharePoint 2010 implementation stalled out of the gate.
In the meantime, some content was put on Box and other services to address external collaboration needs. Business users needed more relevant search results, content databases had grown uncomfortably large, and access controls had become spaghetti. Fortunately, site sprawl wasn’t too bad… except that the reason for that was the low adoption.
SharePoint 2013 arrived to a perfect storm – business and technology needs to be addressed, content that needs to be brought back in-house, and user adoption that needs to be improved. Time to upgrade!
See how we approached the upgrade, the issues than needed to be addressed, and the questions that needed to be answered.
Lessons Learned in the Development of a Web-scale Search Engine: Nutch2 and b...Chris Mattmann
This document summarizes the history and development of the Nutch web search engine project. It discusses how Nutch evolved from its original version to incorporate Hadoop and become more modular by delegating functions like indexing and parsing to other Apache projects like Solr and Tika. The current version, Nutch 2.0, aims to have a slimmed down architecture where it acts as a delegator to these other frameworks rather than handling these functions itself. The document also reflects on lessons learned from earlier stages of the project around community engagement, maintenance, and configuration challenges.
Tips for a successful SharePoint Migration strategyDon Daubert
This document provides tips for a successful SharePoint migration strategy. It discusses various migration options such as in-place upgrades, database attach methods, and third-party migration tools. It emphasizes the importance of discovery and planning, including inventorying the current farm configuration and content. The document also covers implementation, testing the migration plan, and potential issues to watch out for such as metadata not transferring accurately. Post-migration steps are also highlighted like validating content and functionality transferred correctly.
Roles are necessary for successful SharePoint implementations and evolve over time. Initially, core roles include the executive champion to provide buy-in, the platform owner to oversee priorities, and an IT pro to manage servers. As implementations mature, additional roles emerge like developers for customizations, business analysts to understand needs, and site collection administrators to decentralize responsibilities. Scenarios like an intranet require roles like designers for branding, and governance committees to determine policies.
Thinking big with SharePoint the Howard Hughes Way!Vibha Godse Gore
The document summarizes how Howard Hughes Corporation implemented a large SharePoint platform to solve business problems. They migrated over 10 TB of content from file shares and systems into SharePoint sites and libraries. They also automated key business processes using workflows and forms. Challenges included a large content volume, integrating with line of business apps, and adopting users. Now they are planning a migration to Office 365 to leverage modern features while addressing migration of on-prem components like Nintex workflows.
This document provides an overview of SharePoint features and the SharePoint development paradigm. It discusses:
1) The history of SharePoint from 1999 to the present, including versions like SharePoint Server 2001, 2003, 2007, 2010, 2013, and Office 365.
2) Key SharePoint features like social capabilities, document handling, search, business intelligence, mobile access, customization options, and enterprise content management.
3) The SharePoint hierarchy including server farms, web applications, site collections, sites, and lists/libraries.
4) SharePoint development units like site columns, content types, lists, libraries, and pages. Development types including browser, designer, and Visual Studio customization.
This document provides a summary of modern communication sites and customization capabilities. It begins with an overview of where communication sites have evolved from older SharePoint versions. It then discusses how to create communication sites and the out-of-box web parts. Customization options are explained like themes, extensions, and using the SharePoint Framework (SPFx) to build custom web parts. The importance of change management and communication for migrations is stressed. Upcoming features like hub sites and a roadmap for site owners are also mentioned.
SharePoint Saturday Richmond - So you want to implement SharePoint 2010, what...eavanesian
This document provides an overview of factors to consider before implementing SharePoint in an organization. It discusses questions to answer such as having a clear vision, defining critical terms, establishing governance, and developing a communication plan. It also covers assessing organizational readiness through examining support staff, available funding, company culture, and user requirements. Finally, it addresses assessing IT staff availability and ensuring the necessary skills are present, such as network administration, system administration, database administration, and SharePoint development expertise. The key takeaways are that SharePoint implementation requires a paradigm shift and cannot be treated like a typical IT project.
Does your website have a ton of data? How do your users find the relevant pages among all the noise in your site?
Solr can help deliver the pertinent search results to your users regardless of your site's size.
Apache Solr is a Java program that integrates with the Drupal contrib module that allows your users to quickly search millions of records and narrow down the results with minimal system impact.
Redesigning a Website Using Information Architecture PrincipalsJenny Emanuel
This document provides an overview of information architecture concepts for redesigning a library website. It discusses key frameworks like accessibility, usability and balancing context, content and users. The importance of understanding the website context, users, tasks, content and politics is emphasized. Structuring content into areas like information, resources and services is suggested. The document also outlines the agenda, which focuses on frameworks, structuring, organizing, labeling and redesigning a website.
-DSpace Under the Hood-
As presented at OR10 in July 2010-
Part 1: How does DSpace work?: Whilst you don't need to be a mechanic to drive a car, it is helpful if you have a basic understanding of how a car works, what bits do different jobs, and how to top up your oil and pump up your tyres / tires. This presentation will give an overview of the DSpace architecture, and will give you enough knowledge to understand how DSpace works. By knowing this, you will also learn about ways DSpace could be used, and ways in which it can't be used.
Part 2: The development process and YOUR role in it:
DSpace development in undertaken by the DSpace community. No one, or no organisation is in charge, and without contributions from the DSpace community the platform would not continue to develop and evolve. Sometimes it can appear that there are people in charge, or that unless you are a technical developer then there is no way or need to contribute. This presentation will explain how DSpace development usually takes place, where and who has input at different stages, and will equip you to contribute further, or to help you contribute for the first time.
Presenters - members of the DSpace Committers and DSpace Global Outreach Committee:
Lewis, Stuart ; Hayes, Leonie ; Stangeland, Elin ; Shepherd, Kim ; Jones, Richard ; Roos, Monica
Similar to Journey to the center of SharePoint (20)
"Scaling RAG Applications to serve millions of users", Kevin GoedeckeFwdays
How we managed to grow and scale a RAG application from zero to thousands of users in 7 months. Lessons from technical challenges around managing high load for LLMs, RAGs and Vector databases.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
Must Know Postgres Extension for DBA and Developer during MigrationMydbops
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
Twitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
Facebook(Meta): https://www.facebook.com/mydbops/
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Northern Engraving | Modern Metal Trim, Nameplates and Appliance PanelsNorthern Engraving
What began over 115 years ago as a supplier of precision gauges to the automotive industry has evolved into being an industry leader in the manufacture of product branding, automotive cockpit trim and decorative appliance trim. Value-added services include in-house Design, Engineering, Program Management, Test Lab and Tool Shops.
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.
This talk will cover ScyllaDB Architecture from the cluster-level view and zoom in on data distribution and internal node architecture. In the process, we will learn the secret sauce used to get ScyllaDB's high availability and superior performance. We will also touch on the upcoming changes to ScyllaDB architecture, moving to strongly consistent metadata and tablets.
High performance Serverless Java on AWS- GoTo Amsterdam 2024Vadym Kazulkin
Java is for many years one of the most popular programming languages, but it used to have hard times in the Serverless community. Java is known for its high cold start times and high memory footprint, comparing to other programming languages like Node.js and Python. In this talk I'll look at the general best practices and techniques we can use to decrease memory consumption, cold start times for Java Serverless development on AWS including GraalVM (Native Image) and AWS own offering SnapStart based on Firecracker microVM snapshot and restore and CRaC (Coordinated Restore at Checkpoint) runtime hooks. I'll also provide a lot of benchmarking on Lambda functions trying out various deployment package sizes, Lambda memory settings, Java compilation options and HTTP (a)synchronous clients and measure their impact on cold and warm start times.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
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 .
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
1. Journey to the
center of
SharePoint
Voyage au centre de la SharePoint
Vasu Srinivasan, NIC, Texas.gov
Austin SharePoint Users Group (ASPUG)
2. about:me
Vasu Srinivasan
M.S. Computer Science, Russia (c. 1990s)
Senior Technology Consultant, Texas NIC (Texas.gov)
SharePoint sites contributed to:
texas.gov, oregon.gov, pa.gov and a few intranet/extranet
sites
Twitter & LinkedIn: vasya10
Tech Blog: vasya10.wordpress.com
#AustinSPUG-ger since Jan 2012
3. What can you learn about SharePoint in
10 minutes?
SharePoint is
• a product
• a platform
• a cloud
• an ecosystem
Take a tour of the vibrant SharePoint
eco-system in 10 minutes
6. Continental Crust
The SharePoint continental crust
consists of many continents
• Content Management
• Document Management
• Records Management
• Identity Management
• Business Intelligence and BCS
• Search
• Office365
• Workflow
Several continents are still forming
• Social
• eDiscovery
Creatures that fly over this surface
• MVPs, MCPs, MCAs
• SharePoint Architects
• Bloggers and Tweeters
• Podcasters
• Keynote Speakers
Tools they use
• PowerPoint
• Social Networks
• Surface
Earth’s Continental Crust: Layer of igneous and metamorphic rocks
SharePoint Continental Crust: Layer of ingenious rockstars
7. Oceanic Crust
The SharePoint oceanic crust is also
known as The Farm
Deep under the sea, mostly invisible to
the outside world
Creatures that roam this layer
• SharePoint Admins
• SQL Server Admins
• IIS Admins
• Network Engineers
Primarily composed of several servers
known as DB Servers, App Servers, Web
Front Ends, Search Index Servers etc.
Trespassers
• Developers
Tools used
• PowerShell
• Central Admin
• and many weird tools
Earth’s Oceanic Crust: Part of lithosphere that surfaces in oceanic basins. Primarly composed of
sima, thinner but denser than continental crust.
SharePoint Oceanic Crust: The fundamental crust that supports the ecosystem
8. Mantle
The layer where the SharePoint
solutions reside, and usually are
classified as ootb, 3rd-party, codeplex
and customized
Creatures that roam in this
depth
• Developers
• Designers
Just as an unstable mantle can cause
earthquakes, a poorly formed solution
with unplanned governance and
untested usability can cause
SharePoint-quakes
Tools they use
• Visual Studio
• SharePoint Designer
• NAPA
Earth’s Mantle: Layer between crust and outer-core. Predominantly solid, but behaves like
viscous liquid over a large timeframe.
SharePoint Mantle People: Predominantly nerdy, but behavior-wise very social
9. Outer Core
Right below the Mantle, lies the Outer
core, what in SharePoint world, consists
of site
collections, sites, pages, lists, libraries, d
ocuments etc.
This is the layer where Business Users
have the ability to create sites and
content without having to ask IT Staff
Savvy business users also create their
own workflows and keep IT service out
of their way
Creatures that permeate the
Outer Core
• Power Users
Frequent visitors
• DevOps
Aliens and Occasional visitors
• PowerShell Gurus
• Information Architects
Earth Outercore: Without the outercore, life on Earth would be very different.
SharePoint Outercore: Without the PowerUsers, life on planet SharePoint would be very
different.
10. Inner Core
Most people dwell on the surface of
SharePoint and never realize how
important the inner core is
At the inner core of SharePoint, that is
the most important part of the
SharePoint eco-system, reside the Users
A CMS designed and built keeping the
end-users at the core has a better
chance surviving and appreciated
Creatures of the Inner Core
•
•
•
•
End Users
Your Customers
Your Partners
Your Clients
Creatures that should visit this area
• Everyone
Earth’s inner core: Though appearing homogenous, is not completely uniform.
SharePoint inner core: Though appearing homogenous, is the most varied part of the ecosystem
11. Are we there yet?
The more you learn about
Earth, the more you realize that
it is really such a
wonderful, unique planet in all
the known Universe.
The more you learn about
SharePoint, the more you
realize that it is such a
wonderful, unique Content
Management System, among
many CMS.
Welcome to World of SharePoint