The document presents a functional specification for the first prototype of the PATHS system, which aims to make exploring cultural heritage content enjoyable and easy for users, detailing functions like user accounts, workspaces, searching, creating paths and nodes, tagging, and different types of users including general, registered, and administrators. The specification is based on analysis of user requirements to implement core necessary functions for the first prototype while leaving more complex aspects for future iterations.
Outlook test e mail auto configuration autodiscover troubleshooting tools p...Eyal Doron
Outlook Test E-mail AutoConfiguration | Autodiscover troubleshooting tools | Part 1#4 | Part 21#36
Review the use to the use of the Outlook built-in tool named - Outlook Test E-mail AutoConfiguration for - viewing the content of the Autodiscover session between a client and a server.
This is the first article for a series of Three articles, in which we review different tools for “Autodiscover Troubleshooting scenarios”.
http://o365info.com/outlook-test-e-mail-autoconfiguration-autodiscover-troubleshooting-tools-part-1-of-4-part-21-of-36
Eyal Doron | o365info.com
Presentation given by Mark Hall, University of Sheffield, at EuropeanaTech 2011, Vienna (4 - 5 October) on Aggreating Cultural Heritage Collections using Automatically Generated Topic Hierarchies.
Outlook test e mail auto configuration autodiscover troubleshooting tools p...Eyal Doron
Review the use to the use of the Outlook built-in tool named - Outlook Test E-mail AutoConfiguration for - viewing the content of the Autodiscover session between a client and a server.
This is the first article for a series of Three articles, in which we review different tools for “Autodiscover Troubleshooting scenarios”.
http://o365info.com/outlook-test-e-mail-autoconfiguration-autodiscover-troubleshooting-tools-part-1-of-4-part-21-of-36
Should i use a single namespace for exchange infrastructure part 1#2 part ...Eyal Doron
Should I use a single namespace for Exchange Infrastructure? | Part 1#2 | Part 17#36
Description of a scenario in which we use a single namespace for Exchange infrastructure.
The meaning of the term –“single namespace” – is a scenario in which Exchange infrastructure use the same namespace for internal and external Exchange client described as – single or unified namespace.
http://o365info.com/should-i-use-a-single-namespace-for-exchange-infrastructure-part-1-of-2-part-17-of-36
Eyal Doron | o365info.com
Outlook autodiscover decision process choosing the right autodiscover method ...Eyal Doron
Outlook Autodiscover decision process |Choosing the right Autodiscover method | Part 14#36
Managing the default Outlook Autodiscover flow by using a registry keys such as ExcludeSCPlookup and ExcludeHttpsRootDomain.
http://o365info.com/outlook-autodiscover-decision-process-choosing-the-right-autodiscover-method-part-14-of-36
Eyal Doron | o365info.com
Outlook test e mail auto configuration autodiscover troubleshooting tools p...Eyal Doron
Outlook Test E-mail AutoConfiguration | Autodiscover troubleshooting tools | Part 1#4 | Part 21#36
Review the use to the use of the Outlook built-in tool named - Outlook Test E-mail AutoConfiguration for - viewing the content of the Autodiscover session between a client and a server.
This is the first article for a series of Three articles, in which we review different tools for “Autodiscover Troubleshooting scenarios”.
http://o365info.com/outlook-test-e-mail-autoconfiguration-autodiscover-troubleshooting-tools-part-1-of-4-part-21-of-36
Eyal Doron | o365info.com
Presentation given by Mark Hall, University of Sheffield, at EuropeanaTech 2011, Vienna (4 - 5 October) on Aggreating Cultural Heritage Collections using Automatically Generated Topic Hierarchies.
Outlook test e mail auto configuration autodiscover troubleshooting tools p...Eyal Doron
Review the use to the use of the Outlook built-in tool named - Outlook Test E-mail AutoConfiguration for - viewing the content of the Autodiscover session between a client and a server.
This is the first article for a series of Three articles, in which we review different tools for “Autodiscover Troubleshooting scenarios”.
http://o365info.com/outlook-test-e-mail-autoconfiguration-autodiscover-troubleshooting-tools-part-1-of-4-part-21-of-36
Should i use a single namespace for exchange infrastructure part 1#2 part ...Eyal Doron
Should I use a single namespace for Exchange Infrastructure? | Part 1#2 | Part 17#36
Description of a scenario in which we use a single namespace for Exchange infrastructure.
The meaning of the term –“single namespace” – is a scenario in which Exchange infrastructure use the same namespace for internal and external Exchange client described as – single or unified namespace.
http://o365info.com/should-i-use-a-single-namespace-for-exchange-infrastructure-part-1-of-2-part-17-of-36
Eyal Doron | o365info.com
Outlook autodiscover decision process choosing the right autodiscover method ...Eyal Doron
Outlook Autodiscover decision process |Choosing the right Autodiscover method | Part 14#36
Managing the default Outlook Autodiscover flow by using a registry keys such as ExcludeSCPlookup and ExcludeHttpsRootDomain.
http://o365info.com/outlook-autodiscover-decision-process-choosing-the-right-autodiscover-method-part-14-of-36
Eyal Doron | o365info.com
Ашманов И.С. (2013.04.24) - Информационный суверенитет - новая реальностьmediamera
За последние 10, 15, 20 лет слом суверенитета часто происходит через информационные войны. Если вам удается добиться информационного доминирования в какой-то стране — это все-равно, что господствовать в воздухе. В Ливии все именно так и начиналось: сначала произошел слом информационного суверенитета, вызов цветной революции, а потом небо сделали бесполетной зоной и сломили сопротивление. Таким образом, сегодня, если у вас нет информационного суверенитета, вы можете потерять обычный суверенитет, то есть перестать быть независимым государством.
Что такое цифровой суверенитет? Это право государства определять свою информационную политику самостоятельно, распоряжаться инфраструктурой, ресурсами, обеспечивать информационную безопасность и т.д.
Для того, чтобы построить информационный суверенитет, необходимо иметь единую инфраструктуру: собственные поисковые системы, собственные социальные сети, свои месседжеры, блоги, контентные ресурсы и т.д. Также нужно иметь средства мониторинга персональной среды, средства фильтрации трафика. Для защиты от кибервойн необходимо иметь кибервойска.
Exchange In-Place eDiscovery & Hold | Introduction | 5#7Eyal Doron
Exchange In-Place eDiscovery & Hold | Introduction | 5#7
http://o365info.com/exchange-in-place-ediscovery-hold-introduction-part-5-7
The Exchange In-Place Hold & eDiscovery, is a very powerful tool that can help us to accomplish three main tasks.
1. Search for information (mail items) in single or multiple mailboxes
2. Put specific information on “hold” (enable to save the information for an unlimited time period)
3. Recover deleted mail items
In this article, we will review the logic and the concepts of the Exchange In-Place Hold & eDiscovery toll.
In the next article xx, we will demonstrate how to use the Exchange In-Place Hold & eDiscovery toll for recovering deleted mail items.
Eyal Doron | o365info.com
How does sender verification work how we identify spoof mail) spf, dkim dmar...Eyal Doron
The process of “sender verification”, enables us to distinguish between a legitimate sender versus an attacker who spoof his identity.
In the current article, we will review in details the five available methods that we can use for fighting the phenomena of Spoof mail attack.
http://o365info.com/how-does-sender-verification-work-how-we-identify-spoof-mail-the-five-heros-spf-dkim-dmarc-exchange-and-exchange-online-protection-part-9-of-9
Dealing with a spoof mail attacks and phishing mail attacks a little story ...Eyal Doron
In the current article, I would like to review the chain of events that occurs every time, again and again, in a scenario in which the attacker manages to successfully execute a Phishing mail attack.
The reaction of the involved persons is known in advance, and the sad end of the story is known in advance.
The main goal of the story is - to serve as a wakeup call, so you do not have to be a character in the play of – Phishing mail attack!
Exchange CAS server | Proxy versus redirection | 4#23Eyal Doron
Exchange CAS server | Proxy versus redirection | 4#23
http://o365info.com/exchange-cas-server-proxy-versus-redirection/
Reviewing the concept of - “Proxy” versus “Redirect” in Exchange based environment.
Eyal Doron | o365info.com
User-Centred Design to Support Exploration and Path Creation in Cultural Her...pathsproject
User-Centred Design to Support Exploration and Path Creation in Cultural Heritage Collections, Paula Goodale, Paul Clough, Nigel Ford, Mark Hall, Mark Stevenson, Samuel Fernando, Nikolaos Aletras, Kate Fernie, Phil Archer, Andrea De Polo, Euro HCIR 2012. Pre-print of paper.
In this paper we present the results of the user requirements and interface design phase for a prototype system, designed to enhance interaction with cultural heritage collections
online through means of a pathway metaphor. We present a single user interaction model that supports various work and
information seeking tasks undertaken by both expert and non
-expert users within the context of collection exploration and path creation. The user interaction model is shown to enable seamless movement between interaction modes, with the potential over time to encourage deeper engagement and learning.
The LoCloud Live Support Portal (http://support.locloud.eu) is a gateway for all components of the LoCloud support mechanism provided. The support portal gives LoCloud partners and other interested parties unrestricted public access to:
1. Descriptions of services and applications
2. Technical and end-‐user documentation for all services and applications, and training materials
3. Frequently asked questions that are of relevance to the wider community
4. Help-desk functionality
This is one of 7 reports provided in work package 3: Micro services for small and medium institutions.
Authors:
Odo Benda, Astrid Höller and Gerda Koch
AIT Angewandte Informationstechnik Forschungsgesellschaft mbH
indect report Datensammlung in news reports, weblogs, chatAlexa Rose
Official document / INDECT:
Report on methodology for collection, cleaning and unified representation of large textual data from various sources: news reports, weblogs, chat.
(XML Data Corpus)
Ашманов И.С. (2013.04.24) - Информационный суверенитет - новая реальностьmediamera
За последние 10, 15, 20 лет слом суверенитета часто происходит через информационные войны. Если вам удается добиться информационного доминирования в какой-то стране — это все-равно, что господствовать в воздухе. В Ливии все именно так и начиналось: сначала произошел слом информационного суверенитета, вызов цветной революции, а потом небо сделали бесполетной зоной и сломили сопротивление. Таким образом, сегодня, если у вас нет информационного суверенитета, вы можете потерять обычный суверенитет, то есть перестать быть независимым государством.
Что такое цифровой суверенитет? Это право государства определять свою информационную политику самостоятельно, распоряжаться инфраструктурой, ресурсами, обеспечивать информационную безопасность и т.д.
Для того, чтобы построить информационный суверенитет, необходимо иметь единую инфраструктуру: собственные поисковые системы, собственные социальные сети, свои месседжеры, блоги, контентные ресурсы и т.д. Также нужно иметь средства мониторинга персональной среды, средства фильтрации трафика. Для защиты от кибервойн необходимо иметь кибервойска.
Exchange In-Place eDiscovery & Hold | Introduction | 5#7Eyal Doron
Exchange In-Place eDiscovery & Hold | Introduction | 5#7
http://o365info.com/exchange-in-place-ediscovery-hold-introduction-part-5-7
The Exchange In-Place Hold & eDiscovery, is a very powerful tool that can help us to accomplish three main tasks.
1. Search for information (mail items) in single or multiple mailboxes
2. Put specific information on “hold” (enable to save the information for an unlimited time period)
3. Recover deleted mail items
In this article, we will review the logic and the concepts of the Exchange In-Place Hold & eDiscovery toll.
In the next article xx, we will demonstrate how to use the Exchange In-Place Hold & eDiscovery toll for recovering deleted mail items.
Eyal Doron | o365info.com
How does sender verification work how we identify spoof mail) spf, dkim dmar...Eyal Doron
The process of “sender verification”, enables us to distinguish between a legitimate sender versus an attacker who spoof his identity.
In the current article, we will review in details the five available methods that we can use for fighting the phenomena of Spoof mail attack.
http://o365info.com/how-does-sender-verification-work-how-we-identify-spoof-mail-the-five-heros-spf-dkim-dmarc-exchange-and-exchange-online-protection-part-9-of-9
Dealing with a spoof mail attacks and phishing mail attacks a little story ...Eyal Doron
In the current article, I would like to review the chain of events that occurs every time, again and again, in a scenario in which the attacker manages to successfully execute a Phishing mail attack.
The reaction of the involved persons is known in advance, and the sad end of the story is known in advance.
The main goal of the story is - to serve as a wakeup call, so you do not have to be a character in the play of – Phishing mail attack!
Exchange CAS server | Proxy versus redirection | 4#23Eyal Doron
Exchange CAS server | Proxy versus redirection | 4#23
http://o365info.com/exchange-cas-server-proxy-versus-redirection/
Reviewing the concept of - “Proxy” versus “Redirect” in Exchange based environment.
Eyal Doron | o365info.com
User-Centred Design to Support Exploration and Path Creation in Cultural Her...pathsproject
User-Centred Design to Support Exploration and Path Creation in Cultural Heritage Collections, Paula Goodale, Paul Clough, Nigel Ford, Mark Hall, Mark Stevenson, Samuel Fernando, Nikolaos Aletras, Kate Fernie, Phil Archer, Andrea De Polo, Euro HCIR 2012. Pre-print of paper.
In this paper we present the results of the user requirements and interface design phase for a prototype system, designed to enhance interaction with cultural heritage collections
online through means of a pathway metaphor. We present a single user interaction model that supports various work and
information seeking tasks undertaken by both expert and non
-expert users within the context of collection exploration and path creation. The user interaction model is shown to enable seamless movement between interaction modes, with the potential over time to encourage deeper engagement and learning.
The LoCloud Live Support Portal (http://support.locloud.eu) is a gateway for all components of the LoCloud support mechanism provided. The support portal gives LoCloud partners and other interested parties unrestricted public access to:
1. Descriptions of services and applications
2. Technical and end-‐user documentation for all services and applications, and training materials
3. Frequently asked questions that are of relevance to the wider community
4. Help-desk functionality
This is one of 7 reports provided in work package 3: Micro services for small and medium institutions.
Authors:
Odo Benda, Astrid Höller and Gerda Koch
AIT Angewandte Informationstechnik Forschungsgesellschaft mbH
indect report Datensammlung in news reports, weblogs, chatAlexa Rose
Official document / INDECT:
Report on methodology for collection, cleaning and unified representation of large textual data from various sources: news reports, weblogs, chat.
(XML Data Corpus)
Final Report on Petascale Systems and Centre Assessment for PRACE. Feeds into PRACE conference that year. Discusses the HPC data center designed by my team which was used as part of the final design and implemented by ETHZ.
http://www.prace-ri.eu/IMG/pdf/d8.4_1ip.pdf
Roadmap from ESEPaths to EDMPaths: a note on representing annotations resulti...pathsproject
Roadmap from ESEPaths to EDMPaths: a note on representing annotations resulting from automatic enrichment - Aitor Soroa, Eneko Agirre, Arantxa Otegi and Antoine Isaac
This document is a case study on using the Europeana Data Model (EDM) [Doerr et al., 2010] for representing annotations of Cultural Heritage Objects (CHO). One of the main goals of
the PATHS project is to augment CHOs (items) with information that will enrich the user’s experience. The additional information includes links between items in cultural collections and from items to external sources like Wikipedia. With this goal, the PATHS project has applied Natural Language Processing (NLP) techniques on a subset of the items in Europeana.
Aletras, Nikolaos and Stevenson, Mark (2013) "Evaluating Topic Coherence Us...pathsproject
Aletras, Nikolaos and Stevenson, Mark (2013) "Evaluating Topic Coherence Using Distributional Semantics” Proceedings of the 10th International Conference on Computational Semantics (IWCS 2013) -- Long Papers, Potsdam, Germany
PATHSenrich: A Web Service Prototype for Automatic Cultural Heritage Item Enr...pathsproject
PATHSenrich: A Web Service Prototype for Automatic Cultural Heritage Item Enrichment, Eneko Agirre, Ander Barrena, Kike Fernandez, Esther Miranda, Arantxa Otegi, and Aitor Soroa, paper presented the international conference on Theory and Practice in Digital Libraries, TPDL 2013
Large amounts of cultural heritage material are nowadays available through online digital library portals. Most of these cultural items have short descriptions and lack rich contextual information. The PATHS project has developed experimental enrichment services. As a proof of concept, this paper presents a web service prototype which allows independent content providers to enrich cultural heritage items with a subset of the full functionality: links to related items in the collection and links to related Wikipedia articles. In the future we plan to provide more advanced functionality, as available offline for PATHS.
Implementing Recommendations in the PATHS system, SUEDL 2013pathsproject
Implementing Recommendations in the PATHS system, Paul Clough, Arantxa Otegi, Eneko Agirre and Mark Hall, paper presented at the Supporting Users Exploration of Digital Libraries, SUEDL 2013 workshop, during TPDL 2013 in Valetta, Malta
In this paper we describe the design and implementation of nonpersonalized recommendations in the PATHS system. This system allows users to explore items from Europeana in new ways. Recommendations of the type “people who viewed this item also viewed this item” are powered by pairs of viewed items mined from Europeana. However, due to limited usage data only 10.3% of items in the PATHS dataset have recommendations (4.3% of item pairs visited more than once). Therefore, “related items”, a form of contentbased recommendation, are offered to users based on identifying similar items. We discuss some of the problems with implementing recommendations and highlight areas for future work in the PATHS project.
Generating Paths through Cultural Heritage Collections Latech2013 paperpathsproject
Generating Paths through Cultural Heritage Collections, Samuel Fernando, Paula Goodale, Paul Clough, Mark Stevenson, Mark Hall and Eneko Agirre. Paper presented at Latech 2013
Cultural heritage collections usually organise sets of items into exhibitions or guided tours. These items are often accompanied by text that describes the theme and topic of the exhibition and provides background context and details of connections with other items. The PATHS project brings the idea of guided tours to digital library collections where a tool to create virtual paths are used to assist with navigation and provide guides on particular subjects and topics. In this paper we characterise and analyse paths of items created by users of our online system.
Supporting User's Exploration of Digital Libraries, Suedl 2012 workshop proce...pathsproject
Workshop proceedings from the International workshop on Supporting Users Exploration of Digital Libraries, SUEDL 2012 which was held at TPDL 2012 (the international conference on Theory and Practice in Digital Libraries), Paphos, Cyprus, September 2012.
The aim of the workshop was to stimulate collaboration from experts and stakeholders in Digital Libraries, Cultural Heritage, Natural Language Processing and Information Retrieval in order to explore methods and strategies to support exploration of Digital Libraries, beyond the white box paradigm of search and click.
The proceedings includes:
"Browsing Europeana - Opportunities and Challenges', David Haskiya
"Query re-writing using shallow language processing effects', Anna Mastora and Sarantos Kapidakis
"Visualising Television Heritage" Johan Ooman et al,
"Providing suitable information access for new users of Digital Libraries", Rike Brecht et al
"Exploring Pelagios: a Visual Browser for Geo-tagged datasets" Rainer Simon et al
PATHS state of the art monitoring reportpathsproject
This document provides an update to an Initial State of the Art Monitoring report delivered by the project. The report covers the areas of Educational Informatics, Information Retrieval and Semantic Similarity relatedness.
Recommendations for the automatic enrichment of digital library content using...pathsproject
Recommendations for the enrichment of digital library content using open source software, PATHS report by Eneko Agirre and Arantxa Otegi
The goal of this document is to present an overall set of recommendations for the automatic enrichment of Digital Library content using open source software. It is intended to be useful for third-parties who would like to offer enrichment services. Note that this is not a step-by-step guide for reimplementation, but an overall view of the software required and the programming effort involved.
Semantic Enrichment of Cultural Heritage content in PATHSpathsproject
Semantic Enrichment of Cultural Heritage content in PATHS, report by Mark Stevenson and Arantxa Otegi with Eneko Agirre, Nikos Aletras, Paul Clough, Samuel Fernando and Aitor Saroa.
The aim of the PATHS project is to enable exploration and discovery within cultural heritage collections. In order to support this the project developed a range of enrichment techniques which augmented these collections with additional information to enhance the users’ browsing experience. One of the demonstration systems developed in PATHS makes use of content from Europeana. This document summarises the semantic enrichment techniques developed in PATHS, with particular reference to their application to the Europeana data.
Generating Paths through Cultural Heritage Collections, LATECH 2013 paperpathsproject
Generating Paths through Cultural Heritage Collections Samuel Fernando, Paula Goodale, Paul Clough, Mark Stevenson, Mark Hall and Eneko Agirre.
The PATHS project brings the idea of guided tours to digital library collections where a tool to create virtual paths are used to assist with navigation and provide guides on particular subjects and topics. In this paper we characterise and analyse paths of items created by users of our online system.
Generating PATHS through Cultural Heritage Collections, Samuel Fernando, Paula Goodale, Paul Clough,
Mark Stevenson, Mark Hall, Eneko Agirre. Presentation given at LaTeCH 2013, ACL Workshop, Sofia, Bulgaria.
Presentation given by Kate Fernie about the PATHS project and the second PATHS prototype at the European Association of Archaeologists conference, Pilsen, September 2013
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Accelerate your Kubernetes clusters with Varnish Caching
PATHS Functional specification first prototype
1. Grant Agreement No. ICT-2009-270082
Project Acronym PATHS
Project full title Personalised Access To Cultural Heritage Spaces
D1.3 Functional Specification for First Prototype
Authors: Phil Archer (i-sieve Technologies)
Contributors:
Mark M. Hall (University of Sheffield)
Paul Clough (University of Sheffield)
Mark Stevenson (University of Sheffield)
Eneko Agirre (EHU/UPV)
Iñaki Alegria (EHU/UPV)
Kate Fernie (MDR Partners)
Project funded under FP7-ICT-2009-6 Challenge 4 – “Digital Libraries and
Content”
Status
Final
Distribution level
Public
Date of delivery
10/10/2011
Type
Report
Project website
http://www.paths-project.eu
Project Coordinator
Dr. Mark Stevenson
University of Sheffield
2. PATHS (ICT-2009-270082)
Change Log
Version Date Amended by Changes
0.1 28-07-2011 Phil Archer Original document, including elements of
design.
0.2 24-08-2011 Phil Archer Advancement on version 1.0
0.3 31-08-2011 Phil Archer Incorporating comments from KF, MS, MH
0.4 08-09-2011 Phil Archer Beginning of restructured version based
on further feedback
0.5 16-09-2011 Phil Archer Continuation to near completion with new
structure
0.6 22-09-2011 Phil Archer Incorporation of comments from EA, IA,
MH. Completion of content, application of
document template etc.
0.6.2 23-09-2011 Phil Archer Fixed a broken link, minor addition to the
Methodology section stating that some
complex functions may be in mock up
only for the first prototype
1.0 09-10-2011 Phil Archer Extended Exec Summary
Page 2
4. PATHS (ICT-2009-270082)
1. Executive Summary
PATHS aims to make it both enjoyable and easy for users to explore cultural heritage
content in digital libraries.
One of the first steps to achieving this objective was collecting and analysing user
requirements which are presented in D1.1. This deliverable presents the functional
specification for the first prototype of the PATHS system. It supports the project
strategy to bring users into an agile and iterative development cycle by:
Gathering and analysing user requirements;
Developing functional specifications for prototypes;
Evaluating prototypes and reviewing the results to inform the next phase in
the development.
The functional specification presented in this deliverable is based on the user
requirements which were gathered during the first six months of the project.
Together with the System Architecture Specification (D.3.1) it informs the
development of the first PATHS prototype, which will be evaluated during year two of
the project.
During interviews, potential users expressed opinions that were translated into a
series of requirements with three levels of priority: Must, Should and Could. All the
requirements identified in the study have been reviewed in preparing the functional
specification of the first prototype. As far as possible, all 'Must' and 'Should'
requirements will be met in the first prototype, as well as the 'Could' items that were
easy to incorporate. However, more complex subsystems will be left for inclusion in
the second prototype and final PATHS system. This is part of a research and
development strategy to ensure that the available resources at this stage are directed
to testing and evaluating the functionality of the system with the aim of producing a
usable, robust and extensible system. In this first prototype, some aspects of
functionality such as the personalisation and recommendation systems will be in a
rudimentary stage with more advanced functionality being planned for later
prototypes.
There will be three types of user: general users who are anonymous, registered
users who are logged in to the system, and administrators.
General users will be able to search and explore the collections. Exploring in this
context means that they will be able to follow Paths - annotated sequences of objects
- and see links from objects to related resources. Where possible, the system will
attempt to recommend further objects that the user will find interesting, however, the
scope for this among unregistered users (or registered users who are not logged in)
is very small since there is very little available data about the individual.
The interactive functions are primarily available to registered users who are
encouraged to delve deeply into the collections and to share their knowledge and
enthusiasm. Each user will have a workspace in which they can save and annotate
objects and it is from this workspace that they will be able to select objects from the
collection and create Paths. Each node in the Path comprises the object, the Path
creator's notes about the object, and information linking the current node with the
next one. Creating a Path may be completed in a single session or across multiple
sessions - the system will preserve state between visits of each registered user. In
addition to creating Paths, registered users will be able to comment on, tag and rate
Page 4
5. D1.3 Functional Specification of the First Prototype
other people's Paths. If the creator of a Path allows it, registered users will be able to
clone, edit and republish the Path as their own.
At the time of creation, Paths will only be visible to their creator. However, they can
be made available to groups of users or the public. Likewise, registered users will be
able to control the visibility of information contained in their personal profile. Some
will want to be open about themselves, others will with to be more private.
Since the system allows any user to register and to start adding their comments,
administrators will be able to edit or delete user-generated content.
This deliverable consists of:
Chapter 2: Introduction. This chapter sets the context for this functional
specification and describes the work which has been carried out to gather and
analyse requirements.
Chapter 3: Methodology. This chapter describes how the user requirements have
been distilled to provide the functional specification for the first prototype and plans
for the second prototype and other applications.
Chapter 4: Implementation expectations. A series of functions have been
identified for implementation in the first prototype, however the initial implementation
may be in a manual process with automation in the second prototype following user
evaluation.
Chapter 5: Functions derived from the user requirements. This chapter sets out
in detail the functions identified through the user requirements analysis work.
Chapter 6: System functions. This chapter sets out the functions which are
needed by the system in order to meet the user requirements. These functions
include:
Visualise/brows
Access object similarity data
Calculate paths relatedness
Behavioural logging and classification
Recommendations
Chapter 7: Access control. This chapter describes the classes of user and their
privileges in the PATHS system. The three main classes are:
General user
Registered user
Administrator
Chapter 8: Conclusion. This chapter provides a brief summary of the deliverable.
Appendices – The appendices list the user requirements by priority.
Page 5
6. PATHS (ICT-2009-270082)
2. Introduction
PATHS - Personalised Access to Cultural Heritage Spaces - is being designed not
just to make it easy to access cultural heritage but to make it rewarding. Educators
and curators will have a powerful tool for teaching and engaging an audience, users
will be able to explore and share ideas, knowledge and perspectives. PATHS will
present them with the cultural heritage collections and related material, making
recommendations and suggestions for what to look at next, and those
recommendations will be based in part on the user's own tastes and interests.
This is not a simple system. There are multiple data sources, multiple types of user
and multiple tasks that need to be supported.
In the first phase of the PATHS project, partners conducted an extensive survey of
the potential users of the system. These included face to face interviews and an
online survey that were synthesised into a detailed research document, D1.1. As part
of that process, use cases were prepared from which a set of user requirements
were derived. This document takes those requirements and moves the process onto
the next step which is to interpret them as functions within a system.
This document specifies what the first prototype of the PATHS system will do,
complemented by D3.1, the Specification of the System Architecture, which defines
how it will be realised in substantial detail.
Page 6
7. D1.3 Functional Specification of the First Prototype
3. Methodology
Section 10, which forms an appendix to the main body of this document, lists all the
user requirements that were identified in the analysis presented in D1.1. These are
organised by priority (MUST, SHOULD and COULD) and faithfully record the wishes
of the target audience. Unsurprisingly, different users put different priorities on some
functions than others and there was a good deal of repetition but the amount of
rationalisation carried out was deliberately minimal so that the users' wishes have
been reflected as fully as possible.
However, the aim of this document is to provide a working functional specification for
the first prototype of the PATHS system to enable the evaluation of key functionality
by end-users. The project has adopted an agile and iterative development
methodology and a second prototype will be developed later in the project. Thus not
all the user requirements are implemented in this specification. Section 5 therefore is
a distillation of the user requirements taking into account several additional factors:
1. the importance of providing and proving the core system as a basis for
evaluation and in a way that allows for it to be extended in the system
development cycle;
2. dependencies between requirements;
3. the available time and resources.
Functions are grouped into related areas and for each section, a justification for the
choice of functions to be implemented in the first prototype is provided. This is
followed by specific references to the user requirements that are detailed in section
10, organised by MUST, SHOULD, and COULD priorities. Care has been taken to
ensure that all user requirements are included.
In addition to the functions that were identified by the user survey there are also a
series of additional functions are necessary for the system to work. These are set out
in sections 6 & 7 and do not relate directly to the user requirements.
Page 7
8. PATHS (ICT-2009-270082)
4. Implementation Expectations
It is expected that the first prototype will implement each of the functions marked by
an , however, the level of implementation may vary. In the first instance
implementation may rely on manual intervention with automation of the feature
following evaluation in the second prototype.
5. Functions Derived from the User Requirements
5.1. User Accounts
Users will be able to register on the system, thus creating a profile.
Users will be able to login using a username and password combination.
Users will be able to logout.
A system will be implemented that will reminder users if they forget their
password.
Users will be able to edit their profile.
The user will be able to control which aspects of their profile are visible to the
public.
In addition to standard fields such as user name and so on, the profile will
automatically record various aspects such as:
- Paths they have created;
- groups of which they are a member (see 7.4 Groups)
- whether they are a user or facilitator, meaning a teacher, cultural heritage
curator etc.
- their cognitive style: such as rambler, trekker, explorer (see 6.4 Behavioural
Logging & Classification);
- licences/permissions to view items in specific collections (see 5.4 Objects)
- their e-mail address (important for 5.12.2 Communication)
Users will be able to delete their account entirely. This will remove their Paths
and all contributed content (see 5.10 Identity).
5.1.1. Justification
These core functions of user registration and profile management are all listed as
requirements that MUST be fulfilled. It is important that the data structure used in the
first prototype is able to support an extensible list of fields.
Page 8
9. D1.3 Functional Specification of the First Prototype
5.1.2. Original User Requirements
MUST
10.1.1 Registration - Users will be able to register on the PATHS system and gain
privileges.
10.1.2 Profile - Registered Users will have an associated profile.
10.1.3 Edit Profile - Users will be able to edit aspects of their profile
10.1.4 Visibility of profile - Path creators must be able to edit their Paths after
publication
10.1.24 User identity - Users who are not Path creators have an identity on the
system
SHOULD
None
COULD
None
5.2. Workspace
Users will be able to add objects, such as those presented in search results, into
a personal workspace.
Users will be able to rearrange and annotate the objects within the workspace.
5.2.1. Justification
The concept of the individual's workspace is closely associated with a user's profile.
It acts as a notepad where users can collect objects they find interesting, they can
drag objects around to reorder them, and annotate them. This is useful tool for
collecting and organising thoughts as a precursor to creating Paths.
Since the workspace reflects the user's tastes and interests, it is a potential source of
data for the personalisation aspects of the system.
The ability to add any Web resource to a PATHS workspace requires the
development of a browser bookmarklet1 or add-on which is not considered essential
for development alongside the first prototype.
5.2.2. Original User Requirements
MUST
10.1.7 Collect Objects - Objects can be added to and made available directly from
some sort of holding space/workspace
1
http://en.wikipedia.org/wiki/Bookmarklet
Page 9
10. PATHS (ICT-2009-270082)
SHOULD
10.2.2 Organise Personal Collection - It must be possible to annotate, edit and
arrange objects within the holding space/workspace.
COULD
10.3.1 Add any resource to holding space - Users can activate a control in their
browser that adds the current page, whatever its location on the Web, to their
workspace.
5.3. Search
The user will be able to select what s/he wishes to search. Options will be to
search:
- the collections;
- the user's workspace;
- for objects only, Paths only, or both
- on user-generated tags (see 5.8).
Users will be able to save searches to their workspace. The saved search will be
labelled with the search term used.
5.3.1. Justification
A search function is clearly essential for any user, as is the ability to choose where to
search. Being able to collect and organise information is a core part of the PATHS
functionality.
5.3.2. Original User Requirements
MUST
10.1.5 Search the collection - Users can search all objects in the collections within
PATHS.
10.1.8 Search workspace - Users can search their workspace.
10.1.9 Search Paths by topic - Users will be able to search for Paths.
10.1.10 Save searches - Users will be able to save their searches.
SHOULD
10.2.11
Page 10
11. D1.3 Functional Specification of the First Prototype
Search via tags - Users can search collections based on user-generated tags (see
5.8)
10.2.14 Time factor - When searching for Paths, users can specify a preferred
duration for the Paths.
COULD
None
5.3.3. First Prototype
5.4. Objects
Where available, links will be made from objects to their original source, typically
a high resolution image, audio recording or video.
System administrators will be able to record in a user's profile that the user has
access to the Alinari collection. When an authorised user follows a link from an
object to the relevant Alinari image, they will have access. If a user without
authorisation follows the same link they will be redirected to a page giving
information on how a licence may be purchase.
5.4.1. Justification
Links from objects to related objects is a core function of the PATHS system. Such
links are based on the pre-processing carried out in WP2.
Alinari provides an example of a commercial collection: high resolution images are
only made available to paying customers. It is anticipated that the second prototype
will support a system through which access can be granted to original digital
resources to specific users. However, this is a complex area and not a core function
of the system. In the first prototype, the simplest possible system will be
implemented, one that will require manual editing of the relevant user's profile.
5.4.2. Original User Requirements
MUST
10.1.6 Primary object - Users will have access to the original image or other digital
artefact that the metadata describes. Such access may be subject to licence or
payment terms.
10.1.12 Links to related content - Objects in the collections will be linked to related
content and themes into which the object fits.
SHOULD
10.2.4 No restriction on object type - Objects may include text, images, audio or
video
COULD
None
5.5. Node and Path Creation
Users will be able to create Paths, that is, an annotated linear series of nodes.
Page 11
12. PATHS (ICT-2009-270082)
Therefore users will be able to create nodes. A node includes a pointer to an
object selected from search results or the user's workspace together with an
annotation provided by the Path creator (see 5.7).
Users will be able to add a description of the link to the next node in the Path.
Users will be able to create links to related items without fully integrating these
into a path (if you’re interested in X you might also like to see Y).
Users will be able to return to their Paths and perform edits.
Creators can add metadata that describe their Paths.
Creators can set the visibility of their Paths (see 7.5 Visibility and Privacy)
5.5.1. Justification
The creation of Paths is a core feature of the system. It is how users add value to the
collections by annotating them and linking them together into a narrative. The
concept of a node follows from this: it is a container for the object and the Path
creator's interpretation. Such interpretation may include links to other objects, nodes
or Paths but the first prototype will not support Paths with multiple branches.
5.5.2. Original User Requirements
MUST
10.1.13 Create Paths - Users will be able to create Paths.
10.1.14 Edit Paths - Path creators must be able to edit their Paths after
publication.
10.1.16 Search engine friendly - Paths expose key information about subject
matter.
10.1.18 Describe themes and sub-themes - Users will be able to describe the
themes and sub-themes of a Path.
10.1.23 Permission to clone - The Path creator can declare whether they give
their permission for their Path to be cloned. If they do and the path is cloned, the
original Path creator will be alerted (dependent on 10.2.13 Clone Paths).
SHOULD
10.2.5 Create Paths across multiple sessions - Work on creating a Path can be
carried out across multiple sessions with the system preserving state between
such visits.
10.2.8 Activity description - Path creators can describe the type of activities
included in the Path.
10.2.12 Show/hide annotations - Path creators can choose to show or hide their
annotations, links between nodes etc.
COULD
10.3.8 Web content as object - As well as objects, nodes may point to any Web
content which can be text, images, audio or video.
Page 12
13. D1.3 Functional Specification of the First Prototype
5.6. Cloning
Users will be able to clone a Path if the original creator has given his/her
permission.
The cloned Path is attributed to the new owner.
5.6.1. Justification
Cloning existing Paths is seen as a way for individuals to improve upon an existing
Path that goes beyond simply commenting on the nodes and objects
5.6.2. Original User Requirements
MUST
10.1.23 Permission to clone - The Path creator can declare whether they give
their permission for a Path to be cloned. If it is, the Path owner will be alerted
when such an action takes place.
SHOULD
10.2.13 Clone Paths - Users can clone existing Paths and then edit and publish
them under their own name.
COULD
None
5.7. User-Generated Content
This section covers free-flowing text. Section 5.8 covers the more specialised issue
of Tags.
Users will be able to add text to the system.
Users will be allowed to include markup in the text (so that they can include
hyperlinks).
During the Path creation process (see 5.5 Node and Path Creation), text will be
associated with objects, nodes or Paths as part of the content.
Outside the Path creation process, text will be associated with objects, nodes or
Paths as user comments.
All user-generated text, including tags, will be attributed to its author.
5.7.1. Justification
In order to encourage exploration and foster accidental discovery, it is important that
Paths allows users to contribute their ideas and knowledge whether as Path creators
or consumers. Therefore it is important that all users can add text to the system. For
consumers, these will be comments on an object, node or Path (or perhaps a
comment on a previous contributor's comment). Adding text is core to the process of
creating Paths.
Page 13
14. PATHS (ICT-2009-270082)
The first prototype will therefore allow users to input text which can include markup.
This allows the inclusion of hyperlinks to related content, although it also imposes a
burden on system administrators to ensure content is appropriate (see 7.3
Administrator).
It is anticipated that the second prototype will extend the functionality to allow users
to include other media as well as text.
5.7.2. Original User Requirements
MUST
10.1.7 Collect Objects - Objects can be annotated.
10.1.13 Create Paths - User can add annotations to explain the connections
between the nodes in a Path.
10.1.17Add content - Users will be able to add content.
10.1.19 Add content tied to objects - Users will be able to add annotations,
descriptions, narratives etc. to specific objects.
10.1.20 User comments on Paths - Users will be able to comment on Paths and
augment Paths with their own content.
10.1.21 Attribution - All content added to the system will be attributed to the user
that added it.
SHOULD
10.2.15 User comments on items in a Path - Users can comment on individual
items within a Path.
10.2.3 Flexible design - Allow the same basic tools to be used in different ways.
COULD
10.3.2 Rate Paths - Users will be able to rate Paths
10.3.7 User content - Users can upload their own content, such as images and
video, and save it to their holding area.
5.8. Tags
Users will be able to tag objects, nodes and Paths.
5.8.1. Justification
Although cited in the under requirements as a SHOULD, rather than MUST, the first
prototype will facilitate tagging as:
- technically it is simply a specialisation of user generated content;
- it is well understood by users as a means of making connections between
different ideas and themes;
- tags provide data for the linking and recommending elements of PATHS.
Page 14
15. D1.3 Functional Specification of the First Prototype
5.8.2. Original User Requirements
MUST
None
SHOULD
10.2.1 Familiarity - The user experience will be based on familiar styles and
concepts.
10.2.9 Tagging objects - Users can tag objects in the collection.
10.2.11
Page 15
16. PATHS (ICT-2009-270082)
Search via tags - Users can search collections based on user-generated tags
COULD
None
5.9. Rating
Users will be able to rate Paths.
Users will be able to see aggregate ratings for each Path.
5.9.1. Justification
It is perhaps surprising that the user survey gave the ability to rate Paths a low
priority. However, it is included in the first prototype because:
- it is easy to implement using software modules already available to the
project;
- ratings provide a useful method for ranking search results, the ordering of lists
of elements in a user interface, and input to the recommender system
5.9.2. Original User Requirements
MUST
None
SHOULD
None
COULD
10.3.2 Rate Paths - Users will be able to rate Paths
5.10. Identity
Paths, nodes and user comments will each be assigned a URI (objects in the
collection already have their own URI).
5.10.1. Justification
Providing URIs for all data components allows them to be referred to flexibly within
the system and visible on the Web in general. This addresses the need for PATHS to
be available on multiple platforms. As well as being important for search, it is also
important for administrative monitoring of the content on the system (see 7.3
Administrator). Giving URIs to each data object also greatly aids the design of a User
Interface that fosters a sense of discovery (5.11).
5.10.2. Original User Requirements
MUST
10.1.15 Identity - Paths, nodes, user comments & contributions must have a
unique identity that can be referenced on the Web.
10.1.16 Search engine friendly - Paths are search-engine friendly
Page 16
17. D1.3 Functional Specification of the First Prototype
10.1.25 Multiple platforms - The PATHS system will be available through multiple
platforms.
SHOULD
10.2.3 Flexible design - PATHS should use a flexible design, allowing the same
basic tools to be used in different ways.
COULD
None
5.11. Discovery
Users will be able to follow links from one object to related objects and/or
resources on the Web (see also 5.4)
Users will be able to chose to switch to another Path whenever they are at an
intersecting node or one that is thematically nearby.
Users will be able to change direction, either to retrace their steps or simply follow
the path backwards, or follow links to related material.
Users may join and leave a Path at any point and may come back and
recommence their journey where they left off.
5.11.1. Justification
These functions are all about engaging the user, allowing them to follow their
interests. Their implementation is largely at the User Interface layer rather than in the
data layers.
5.11.2. Original User Requirements
MUST
10.1.11 Find existing Paths - users will be able to discover existing Paths (via
means other than search).
10.1.26 Zoom - Users will be able to view a Path at different resolutions
10.1.27 Sense of discovery - Users will have a good deal of flexibility in how they
use the PATHS system.
SHOULD
10.2.1 Familiarity - The user experience will be based on familiar styles and
concepts.
COULD
None
5.12. User Requirements Not Covered
The preceding subsections are drawn directly from the user requirements. A small
number of these remain uncovered so far however. These are discussed in the
following short subsections.
Page 17
18. PATHS (ICT-2009-270082)
5.12.1. Access Control
10.1.22 Grant access to specific users & user and 10.1.28 Delete user profiles and
user-generated content, 10.2.6 Grant access to specific groups are all covered in
section 7.3 Administrator.
5.12.2. Communication
10.2.7 Communication with Path creator and 10.3.3 Receive private comments are
both covered by way of the provision of the Path creator's e-mail address in their
profile (5.1User Accounts). The provision of a messaging system within PATHS, the
primary purpose of which would be to allow communication without revealing e-mail
addresses, would be a disproportionate use of resources.
5.12.3. Advanced Exploitation of Tagging
10.2.10 Aggregate tags and 10.3.4 Tag rewards both refer to the notion of Luis von
Ahn's ESP Game2 where game-play is used to encourage users to tag objects. When
multiple players tag the same item the same way, they are rewarded in some way as
the tag is more likely to be useful to other people. This would require significant
investment in time and resources to implement on the PATHS system and is not
foreseen as a feature of the first or second prototype.
5.12.4. Geolocation
10.3.5 Geolocation data and 10.3.6 Matching Paths and objects to locations are both
concerned with exploiting location data in the metadata. Processing work already
carried out on the Europeana data set suggests that this is rarely present although
the potential is such that the issue will be re-examined for the second prototype.
2
http://en.wikipedia.org/wiki/ESP_Game
Page 18
19. D1.3 Functional Specification of the First Prototype
6. System Functions
In addition to the functions that are revealed by analysing the user requirements,
there are a number that are either implied or that are required in order to make the
system operable at a suitably robust level. Rather than user requirements, these can
be thought of as functions required within the system in order to meet the user
requirements. These are all effectively at the level of MUST.
6.1. Visualise/Browse the System
Users will be able to browse the collection, follow Paths, follow links to related
items
6.1.1. Justification
This function is included to indicate that PATHS will have a user interface through
which the system will be accessible, something not explicitly set out in section 5.
6.2. Access Object Similarity Data
The PATHS system will be able access the data processed in work package 2 in
which the similarity between objects is calculated, along with links to external
resources. This is the engine behind the requirement that objects will link to
related items.
6.2.1. Justification
This 'obvious' function is included for the sake of completeness.
6.3. Calculate Path Relatedness
The system will be able to calculate the relatedness of Paths.
6.3.1. Justification
This is necessary in order to perform the functions set out in section 5.11 Discovery.
6.4. Behavioural Logging & Classification
The system will record users' behaviour: click rate, subjects viewed, links
followed, search terms used etc.
Based on the behavioural log, the system will be able to classify the user, with
increasing accuracy, as a rambler trekker, explorer.
For registered users, the cognitive style classification will be recorded in their
profile (see 5.1 User Accounts).
6.4.1. Justification
This is an important aspect of the personalisation algorithm used by Paths.
6.5. Recommendations
A critical part of PATHS (Personalised Access to Cultural Heritage Spaces) is the
ability for the system to recommend objects and Paths to a user based on their
cognitive style and interests. This will not be implemented in the first prototype but
will be in the second.
Page 19
20. PATHS (ICT-2009-270082)
6.5.1. Justification
This function is at the core of PATHS, however, it is necessary to build the basic
system and see what data can reasonably be collected from users before detailed
work on this module can be carried out.
Page 20
21. D1.3 Functional Specification of the First Prototype
7. Access Control
In order to function securely and flexibly, PATHS requires three different classes of
user:
1. General user: An anonymous user who has not registered an account or not
logged into their account.
2. Registered user: A user who has registered an account and logged into this
account.
3. Administrator: An administrative user.
Each of these three classes provides different privileges (see following sections). In
addition, PATHS supports the concept of groups
7.1. General Users
General users are anonymous users who have either not registered an account
on the system or have not logged into their account. They have access to the
following functionalities:
Search the collections (section 5.3 Search).
Explore the collections (section 5.11 Discovery).
Search the published paths (section 5.3 Search ).
Follow published paths (section 6.1 Visualise/Browse the System)
View individual nodes and objects (section 5.10 Identity).
View user-comments on nodes, objects, or paths (section 6.1
Visualise/Browse the System).
View the public sections of registered users' profiles (section 6.1
Visualise/Browse the System).
Register an account (section 5.1 User Accounts).
Log in to an existing account (section 5.1 User Accounts). This action makes
the user a registered user.
Search engines or other web-crawlers are also classified as general users and the
same access rights apply to them.
7.2. Registered Users
Registered users have created an account and logged in to their account. They
inherit all the access rights that a general user has. Additionally they have access
to the following functionalities:
Add items to their workspace (section 5.2 Workspace).
Create paths (section 5.5 Node and Path Creation).
Edit their own paths (section 5.5 Node and Path Creation).
Clone other paths (section 5.6 Cloning).
Edit their profile (section 5.1 User Accounts).
Log out (section 5.1 User Accounts). This action makes the user a general
user.
Delete their account (section 5.1 User Accounts).
Add tags to objects, nodes, Paths (section 5.8 Tags ).
Add comments to objects, nodes, paths (section 5.7 User-Generated
Content).
Create, join, leave user groups (section 7.4 Groups).
Access groups of which they are a member (section 7.4 Groups).
Page 21
22. PATHS (ICT-2009-270082)
7.3. Administrator
The administrator is a super-user who inherits all the registered users access
rights. Additionally they have access to the following functionalities:
Edit or delete any Path.
Edit or delete any user account.
Edit or delete any user-comment (section 5.10 Identity).
Edit or delete any user-generated tag.
Edit or delete any user-group (section 7.4Groups).
Access any group (sect. X.Y.Z)
7.4. Groups
Registered Users may create, join and leave groups.
Users can see a list of members of groups of which they themselves are a
member.
7.4.1. Justification
It is useful for some Path creators, particularly teachers, to be able to create and
maintain groups, which are a shortcut route to making Paths available to particular
users.
Support for groups in the first prototype will be simple but it is envisaged that the
second prototype will support more advanced functions. In particular, a distinction
between open groups that anyone can join, groups that are only open to invited
members and groups to which users are assigned by the creator.
7.5. Visibility and Privacy
Users may set the visibility of their contributions to one of three levels:
- private (user only)
- group (visible to any group of which the user is a member)
- public.
Users can set visibility controls for:
- each item in their profile except their username & password;
- the Paths they create;
- comments they have made;
- their workspace.
7.5.1. Justification
User requirement 10.2.12 Show/hide annotations suggests that Path creators
SHOULD be able to show or hide annotations on an individual Path. Although
desirable for a later prototype, this fine-grained control will not be implemented in the
first prototype where the emphasis is on proving the system. Nevertheless, it is
important that the first prototype has sufficient flexibility to give users good control
over their privacy so as to engender trust in the system.
Page 22
23. D1.3 Functional Specification of the First Prototype
8. Conclusion
The functions detailed in sections 5-7 describe a complex system with many facets.
Where possible, the requirements suggested by the users have been
accommodated. Where necessary, the requirements have been managed in a way
that allows for evaluation of functionality and development to within the agile and
iterative research cycle adopted in this project.
9. References
Other important documents from the PATHS deliverables include:
D1.1 User Requirements Analysis
D3.1 Specification of System Architecture
Public project deliverables will be published on the project website at:
http://www.paths-project.eu/eng/Resources
Page 23
24. PATHS (ICT-2009-270082)
10. Appendix: User Requirements by Priority
The user requirements for PATHS were established in section 8.3 of D1.1. These are
replicated in the following sections according to priority (MUST, SHOULD and
COULD). The heading of each requirement serves as an identifier for reference in
the main body of this document. Explanatory text is provided along with a cross
reference to its original source in D1.1. For example "p124/5" means that the original
user requirement is given on page 124 of D1.1 and its "Use Case Reference" is 5.
This refers to the points within the use cases that precede the summary tables of
requirements.
10.1. MUST
The following user requirements are those with the highest priority and that must be
met in the first prototype of the PATHS system.
10.1.1. Registration
Users will be able to register on the PATHS system and gain privileges
Source: p132/pA1
Tags Users, Access
10.1.2. Profile
Registered users will have an associated profile that, in addition to standard fields
such as user name, e-mail address and so on will record various aspects such as:
- Paths they have created;
- groups of which they are a member;
- whether they are a user or facilitator;
- their cognitive style (rambler, trekker, explorer).
Source: p132/A2 & A3
Tags: Users
10.1.3. Edit Profile
Users will be able to edit aspects of their profile. However, some details, such as the
Paths they have created, will be calculated by the system and will not be editable.
Source: p132/A2
Tags: Users
10.1.4. Visibility of profile
The user requirements imply, but do not explicitly state, that the user will be able to
choose which aspects of their profile are visible.
Tags: Users
Page 24
25. D1.3 Functional Specification of the First Prototype
10.1.5. Search the collection
Users can perform a free text search all objects in the collections within PATHS.
Source: p124/5
Tags: Search
10.1.6. Primary object
PATHS will do its processing based on metadata, however, users will also have
access to the original image or other digital artefact that the metadata describes. If
such access is subject to licensing agreement, subscription or other condition,
following the link will direct the user to a page giving details of the terms under which
the object is available and how to meet them (where to agree to the terms, where to
buy the subscription etc.).
Source: p137/D13
Tags: Access, Object
10.1.7. Collect Objects
Objects can be added to and made available directly from some sort of holding
space/workspace. Objects can be annotated. See also 10.2.1
Source: p124/5 p133/B5
Tags: Workspace, UGC
10.1.8. Search workspace
Registered users, who may be Path creators, can search within their own holding
area.
Source: p133/B1
Tags: Search, Workspace
10.1.9. Search Paths by topic
The user requirement states that registered users can search for objects via related
Paths. For the first prototype we interpret this to say that all users (registered or not)
should be able to search for Paths about a given topic.
Source: p133/B1
Tags: Search, Paths
10.1.10. Save searches
Users will be able to save their searches.
Source: p137/D15
Tags: Search
Page 25
26. PATHS (ICT-2009-270082)
10.1.11. Find existing Paths
Closely allied to 10.1.9, users will be able to discover existing Paths (via means other
than search).
Source: p133/B4
Search: Discovery
10.1.12. Links to related content
Objects in the collections will be linked to related content and themes into which the
object fits.
Sources: p124/5, p133/B3, p126/3
Tags: Objects
10.1.13. Create Paths
Users will be able to create Paths, that is, an annotated series of nodes. A node
includes a pointer to an object from a collection together with an annotation provided
by the Path creator and a description of the link to the next node in the Path.
Source: p124/8 (this talks about objects but later requirements modify this to talk
about nodes), p134/C4
More specifically, users will be able to:
select items from search results and add them to a Path in an organised way,
e.g. identifying nodes, connections between nodes, the main pathway and
branches (this implies the existence and minimum functionality for the user's
workspace, see 10.1.7);
add annotations to explain the connections between the nodes in a Path;
create links to related items without fully integrating these into a path (if you’re
interested in X you might also like to see Y).
Source: p134/C1
Tags: Path Creation
10.1.14. Edit Paths
Path creators must be able to edit their Paths after publication. This includes the
ability to insert new nodes and delete existing ones. See also 10.2.5.
Source: p134/C7 & C8
Tags: Path Creation
10.1.15. Identity
Paths, nodes, user comments & contributions must have a unique identity that can
be referenced on the Web.
Sources: p124/9 and 10, p131/2, p135/C16, C17, p137/D15
Page 26
27. D1.3 Functional Specification of the First Prototype
Tags: UGC, Access, Architecture
10.1.16. Search engine friendly
Paths are search-engine friendly, i.e. they expose key information about the Path’s
subject matter etc. See also 10.1.18
Source: p127/1, p136/D10
Tags: Architecture, Paths
10.1.17. Add content
Users will be able to add content. As a minimum, this will be as plain text although
hypertext, images and audio/video should also be considered.
Source: p124/Note on Point 7, p134/C6, p137/D12
Tags: UGC
10.1.18. Describe themes and sub-themes
Users will be able to describe the themes and sub-themes of a Path. This is related
to the Path, not any specific object within the Path. See 10.1.17.
Source: p124/7a, p143/C5, p137/E1
Tags: Path Creation
10.1.19. Add content tied to objects
Users will be able to add annotations, descriptions, narratives etc. to specific objects.
See section 10.1.17
Source: p124/7b
Tags: UGC
10.1.20. User comments on Paths
Users will be able to comment on Paths and augment Paths with their own content.
See also 10.2.15 which extends this functionality to comment on individual nodes.
Sources p126/5, p124/8a & 8b, p129/5b, p136/D6
Tags: UGC
10.1.21. Attribution
All content added to the system will be attributed to the user that added it. This
includes tags, comments, annotations, Paths and, if supported, uploaded images etc.
(see 10.3.7). Attribution will be visible to users.
Source: p137/D12, E2
Tags: UGC, Access
Page 27
28. PATHS (ICT-2009-270082)
10.1.22. Grant access to specific users & user groups
By default, a Path is only visible to its creator. However, the user can choose to make
it available to:
other specific users;
specific groups of which the user is a member;
all users;
the public.
Source: p126/5, p126/6&8, p135/C10. See also 10.2.6, 10.2.12
Tags: Path Creation, Access
10.1.23. Permission to clone
If 10.2.13 is implemented, Paths may be cloned by a user, edited and republished as
their own. The Path creator can declare whether they give their permission for this. If
a Path is cloned, the Path owner will be alerted.
Source: p135/C15
Tags: Clone, Path Creation
10.1.24. User identity
Users who are not Path creators have an identity on the system
Source: p129/5
Tags: Users, Access
10.1.25. Multiple platforms
The PATHS system will be available through multiple platforms.
Source: p131/1, p137/E4
Tags: Architecture
10.1.26. Zoom
Users will be able to view a Path at different resolutions so that they can see an
overview or focus on a particular node.
Source: p131/6, p136/D1
Tags: UI
10.1.27. Sense of discovery
To foster a sense of discovery each object will be linked to related objects in the
collection and resources elsewhere on the Web
Users will be able to choose to switch to another Path whenever they are at an
intersecting node or one that is thematically nearby.
Page 28
29. D1.3 Functional Specification of the First Prototype
Users will be able to change direction, either to retrace their steps or simply follow
the path backwards, or follow links to related material.
Users may join and leave a Path at any point and may come back and recommence
their journey where they left off.
Source: p131/2, p136/D2, D3, D4, D14, D15
Tags: Object, UI, Architecture
10.1.28. Delete user profiles and user-generated content
Administrators will be able to delete any user from the system as well as individual
items such as tags, annotations and, if supported, images and videos (see 10.3.7).
Source: p136/D11
Tags: Access
10.2. SHOULD
10.2.1. Familiarity
The user experience will be based on familiar styles and concepts rather than offer
something entirely novel.
Source: p132/A5
Tags: UI
10.2.2. Organise Personal Collection
It must be possible to annotate, edit and arrange objects within the holding space.
Source: p124/5
Tags: UI
10.2.3. Flexible design
PATHS should use a flexible design, allowing the same basic tools to be used in
different ways. Paths should be accessible and viewable in different ways (see
10.1.26) with support for different types of linking material between nodes.
Source: p124/8, p134/C9
Tags: Architecture, UI
10.2.4. No restriction on object type
Objects may include text, images, audio or video
Source: p131/4 & 7
Tags: Architecture
Page 29
30. PATHS (ICT-2009-270082)
10.2.5. Create Paths across multiple sessions
Work on creating a Path can be carried out across multiple sessions with the system
preserving state between such visits.
Source: p124/8a, p126/6
Tags: UI, Architecture
10.2.6. Grant access to specific groups
Path creators can grant access to a specific Path to a group of users. This does not
imply that the Path creator is in control of that group's membership. Such access can
be rescinded.
Source: p126/5, p126/6&8
Tags: Access, Groups
10.2.7. Communication with Path creator
Uses can communicate directly and privately with a Path creator, at least to alert
them that a comment has been left.
Source: 126/5a, p125/C13
Tags: Comms
10.2.8. Activity description
In addition to the metadata defined in 10.1.18, Path creators can describe the type of
activities includes, the likely time to complete the Path and any other related
information.
Source: p127/6
Tags: Path Creation
10.2.9. Tagging objects
Users can tag objects in the collection. [There's some confusion here since D9 says
'objects in the Path' which may mean nodes rather than objects].
Source: p129/5a, p136/D9
Tags: UGC
10.2.10. Aggregate tags
User-defined tags are aggregated (see 10.2.9)
Source: p129/5a
Tags: Architecture, UI
Page 30
31. D1.3 Functional Specification of the First Prototype
10.2.11. Search via tags
Users can search collections by matching user-generated tags.
Source: p133/B6
Tags: Search
10.2.12. Show/hide annotations
Path creators can choose to show or hide their annotations, links between nodes etc.
Source: p129/5b, p135/C11
Tags: Path Creation, Access
10.2.13. Clone Paths
Users can clone existing Paths and then edit and publish them under their own
name.
Source: p129/5c, p131/10 & 11, p135/C14, p137/E2
Tags: Clone
10.2.14. Time factor
When searching for Paths (10.1.9), users can specify a preferred duration for the
Paths. (see 10.2.8)
Source: p136/D5
Tags: Search
10.2.15. User comments on items in a Path
Users can comment on individual items within a Path.
Source: p124/8b, p136/D7 (the former is COULD, the latter is SHOULD)
Tags: UGC
10.3. COULD
10.3.1. Add any resource to holding space
Users can activate a control in their browser that adds the current page, whatever its
location on the Web, to their workspace.
Source: p126/3, p134/C2
Tags: Architecture
10.3.2. Rate Paths
Users will be able to rate Paths
Page 31
32. PATHS (ICT-2009-270082)
Source: p136/D8, p126/5c (the former has this as COULD, the latter as SHOULD).
Tags: UGC
10.3.3. Receive private comments
A Path creator can receive private comments on their Path.
Source: p126/7, p135/C12
Tags: Comms
10.3.4. Tag rewards
In an application of the ESP game2, users are rewarded for tagging an object in the
same way as others have already done. See 10.2.9 and 10.2.10.
Source: p135/E3
Tags: UGC
10.3.5. Geolocation data
Where available, object metadata should include geolocation data (so they can be
shown on a normal map).
Source: p131/3
Tags: Architecture
10.3.6. Matching Paths and objects to locations
Paths can offer information about objects associated with a specific location and
users can search for content associated with a specific location, perhaps via a map.
Source: p131/9, p133/B2
Tags: Architecture, Search
10.3.7. User content
Users can upload their own content, such as images and video, and save it to their
holding area. Such content must have associated structured metadata.
Although not explicitly stated, the implication is that such content could be used in a
Path. See also 10.1.17.
Source: p131/5, p136/D11
Tags: UGC
10.3.8. Web content as object
Section 10.1.13 requires that nodes link to an object from a collection. Nodes may
alternatively point to any other Web content which can be text, images, audio or
video.
Source: p135/C3
Page 32