Welcome to the ECS Blogging system
Posted by admin in Uncategorized on January 6, 2010
Welcome to the community blog pages for ECS-Electronics and Computer Science at the University of Southampton.
These blogs are written by academic and research staff and students in ECS on a mixture of topics, ranging from progress on undergraduate projects to reflections on current research issues and postgraduate progress notes.
ECS staff and students can register for a blog by filling out the Blog request form.
A collection of latest posts is below – the full list of blogs is on the right.
RedFeather Configuration 1 – Philosophy
Posted by Matt R Taylor in RedFeather on May 16, 2012
One of the greatest barriers when deploying a full-scale repository platform such as EPrints is the amount of configuration required to take the software from its “out of the box” state to something suitable for teaching and learning. Installing the EdShare suite of extensions takes you a great deal of the way by providing simplified workflows, in-browser previews of documents, collections, user profile pages and more. However, tweaking these base settings to perfectly match your requirements still requires a certain familiarity with the inner working of EPrints itself.
With RedFeather we want to try and provide a system that will satisfy the requirements of 90% of users with almost zero configuration – the idea of a repository you can fully deploy in a single afternoon is very appealing to us. Of course, we don’t want something that is not flexible enough to be useful to that final 10% of expert users who want to go the extra mile.
At this point in the project I’ve already done a great deal of work prototyping various different ways of providing customisation, ranging from highly granular configurations where each individual component can be seamlessly interchanged, to complete fixed configurations which are coded to only do exactly what we want. Both approaches have their advantages but the main motivation behind RedFeather is that the system should be simple and forsake all the complexity so inherent in existing repository platforms. This has led me to the following philosophy for the design:
1 ASSUME ONLY MINIMAL VARIATIONS
Cater primarily for the 90% of people who will deploy RedFeather with the default workflow, metadata and look-and-feel but make it easy for them to change very minor parts of the site such as the header, footer and stylesheet.
2 PRIORITISE SIMPLICITY OVER FLEXIBILITY
Do everything in a way so simple that changing it is trivial for anyone with even basic knowledge of html and PHP. Don’t try to anticipate how more advanced users will want to customise the code – just make it easy for them to understand the existing system and leave the rewriting to them.
RedFeather Project Plan
Posted by Matt R Taylor in RedFeather on May 16, 2012
Project Overview
Currently there are significant barriers to individuals or smaller groups publishing OER materials. They can upload their work to a website, but rich media is effectively dark to search engines without adequate metadata, in addition they may forget important licensing information, and materials published this way are invisible to national indexers like Jorum or Xpert. RedFeather (Resource Exhibition and Discovery) is a proposed lightweight repository server-side script that fosters best practice for OER, it can be dropped into any website with PHP, and which enables appropriate metadata to be assigned to resources, creates views in multiple formats (including HTML with in-browser previews, RSS and JSON), and provides instant tools to submit to Xpert and Jorum, or migrate to full repository platforms via SWORD. RedFeather will require no significant technical expertise and no database, but will provide a simple and effective repository solution for smaller projects, individuals, or those seeking to demonstrate OER in order to justify a more significant investment in an organisational repository. RedFeather will be demonstrated and evaluated in collaboration with the University’s Archeological Computing and Digital Economy Research Groups.
Anticipated Outputs and Outcomes
- As well as making the creation of OER materials more straightforward RedFeather will foster OER best practice and fits into a number of the key areas identified by JISC:
- It’s main impact will be to improve resource description, at present OER creators seeking a simple solution merely add their resources to a website, and for rich media types this effectively makes them part of the dark web. Using RedFeather will encourage minimal but significant metadata – such as titles, keywords and licensing information – that will make resources more visible to search engines. In addition the multiple views that will be offered by RedFeather (such as RSS, RDF, and JSON) will make resources far more visible to crawlers and other automated systems.
- In addition RedFeather will be specifically designed to promote and enable aggregation and discovery, by using SWORD to link with key OER indexers such as Xpert and Jorum. RedFeather will provide a lightweight gateway through which users can experiment with OER, and yet still participate with national efforts.
- Finally RedFeather will provide out-of-the-box tools to support social recommendation, encouraging users to use social tools such as Facebook, Twitter or Disqus to highlight and share resources. In addition we plan to develop a recommendation plugin based on the Xpert index, which will instantly link RedFeather resources with similar content from the broader OER context.
We anticipate that the Impact of the RedFeather project will be:
- Access to the benefits of OER sharing are widened to users with small, simple cases without the need for an institutional repository
- Previously hidden resources will become available through access to simple OER good practice, increasing the breadth and number of OER resources.
Overall Approach
The intention is that a base install of RedFeather will be a single .php file which can be dropped into almost any web space to provide quick and straight forward access to digital resources.
Have a look at our blog post: who is RedFeather for? which describes the stakeholders in Redfeather and scenarios of use.
Redfeather features will be extended in collaboration with our co-designers to include tools/plugins for social media, recommenders, WordPress
RedFeather interoperability/standards
To ensure productive use of RedFeather we will adopt these standards:
OER Licensing: information based on appropriate Creative Commons licenses
Export standards: RSS, RDF, JSON
Metadata: Dublin Core
RedFeather Deliverables
- RedFeather Core Plugin Framework
- RedFeather HTML View Plugin
- RedFeather RSS Export Plugin
- RedFeather RDF Export Plugin
- RedFeather JSON Export Plugin
- Social and Recommendation Plugins
The software will be made available through the project website (for at least three years )as an Open Source download and licensed for use under Creative Commons GNU general Public License (software).
Project Resources
RedFeather will take an iterative development approach and work closely with stakeholders in both the ACRG and DE USRG. In larger projects we have undertaken the full participatory design process, and we will borrow the more agile elements for RedFeather, for example including stakeholders in project planning, and adopting an agile approach with user meetings acting as a place where stakeholders can participate in the design process. User’s qualitative comments and personal usage stories will also be a core part of the evaluation of the tool, which will be included in the final project report. This user engagement will enable us to tailor the software according to real requirements and needs, and will ultimately result in not only the software becoming available, but also new OER sites that can contribute to the national OER picture, and act as exemplars of what can be achieved with RedFeather
The RedFeather Project team is:
| Dave Millard | Principal Investigator | dem@ecs.soton.ac.uk |
| Yvonne Howard | Project Manager | ymh@ecs.soton.ac.uk |
| Matt Taylor | Developer | mrt@ecs.soton.ac.uk |
Risk Analysis
| Risk Description | Probability P 1(Low) – 5 (High) | Severity S 1(Low) – 5 (High) | Risk Score (PxS) | Detail of action to be taken
(mitigation / reduction / transfer / acceptance) |
| Delay in employing staff | 1 | 5 | 5 | Given the small timescale a prompt start is critical, however a developer is already in place and there is a very low likelihood of any delays. |
| Technical delays | 2 | 3 | 6 | There is a danger that any tool development will take longer than anticipated, or may fail to fulfil requirements. We consider this to be a low risk because of the skill sets present in the development team, however in the event of any delays it will be possible to reduce the scale of the social plugins planned for WP3 in order to ensure successful delivery of the core RedFeather platform. |
Work packages
As a five-month project RedFeather will follow a simple organisation of three work packages (WP1-3) focused on achieving six explicit deliverables (D1-6), and one workpackage focused on dissemination which continue throughout the project. The work package structure is shown below:
WP1: Development
The first work package will set up our co-design team of developers and members of our stakeholder group. The work package will build the RedFeather core, which allows a user to provide metadata for files and creates HTML pages for each file. All components will be plugins so this core will take the form of a simple plugin framework, and a HTML plugin. This will provide the technology framework for RedFeather. The RedFeather core will be available as an on line perpetual beta for testing/ feedback with our co-design team.
Deliverable 1: RedFeather Core Plugin Framework (M2)
Deliverable 2: RedFeather HTML View Plugin (M2)
WP2: Export Plugins
Once the framework is complete, we will work with our co-design team to create plugins to support our use cases, including export plugins for outputting metadata as RSS, RDF, and JSON. Existing metadata schemes/ontologies (such as Dublin Core) will be used wherever possible. The plugins will be available through the perpetual beta deployment set up in WP1
Deliverable 3: RedFeather RSS Export Plugin (M3)
Deliverable 4: RedFeather RDF Export Plugin (M3)
Deliverable 5: RedFeather JSON Export Plugin (M3)
WP3: Deployment and Social Plugins
Finally RedFeather will be evaluated with our early adopters in the ACRG and DE USRG, and final plugins will be developed for social recommendation (e.g. sharing on Facebook/Twitter, commentary and recommendation via Xpert).
Deliverable 6: Social and Recommendation Plugins (M5)
WP4: Communication and Dissemination
Throughout the project will disseminate RedFeather developments and project progress through the project blog. As well as generating interest with our early adopters, we plan to launch Redfeather to the wider OER and repository community at Repofringe 2011. We hope to be able to take RedFeather to OR11 next year.
Future Work
Posted by jc34g08 in About Sociabubbles on May 11, 2012
There has been a lot of work on Sociabubbles and so far we have shown that it is possible within technical constraints to develop and run this application relatively easily. But there are still things that can be carried out in the future to further improve has already been designed.
Presentation Preparation
Posted by friendswithbenefits in Uncategorized on May 11, 2012
Wow, so that’s our blog done for the meanwhile 
Thanks for viewing, we will be preparing now for the presentation at the Dragons Den, with Raluca Laic and Thomas Reeves-Varndell presenting the proposal, and a demo from Tom Hennigan. Marketing and statistics were covered by Jacky Chen and Kevin Yi.
From the FwB Team, looking forward to pitching this novel and exciting idea to you soon.
Friends With Benefits – “It’s not what you know, it’s who you know!”
Survey results
Posted by Asad in Need of our tool, survey on May 11, 2012
Our survey results clearly signify the need and wants of a closed university network .
The survey was conducted with 60 people , involved in all levels of education ( Undergrad, postgrad and members of staff).
Our survey consisted individuals in all levels of education( Undergraduate, Postgraduate and Members of staff)
This Picture shows that 90% of the survey were conducted by students , we considered people who voted undergraduate or postgraduate in the above figure.
This shows that 86.2% want a closed university social network
This shows that 72.4% are comfortable sharing professional data
This shows that 89.7% people find social network for professional work interesting.
This shows that 89.7% people do not know their colleagues at work/class.
This shows that 62.1% feel that communication can be made better with the creation of a closed university network
connecTTed: user profile
The user profile is inspired by Facebook and LinkedIN. We can find both academic/professional information and general post by the user and his connecTTion.
The top box is probably the most important because it resumes the academic career of the user in order to facilitate other people’s connection.
SotonSocialShare Prototype
Posted by sotonsocialshare in Uncategorized on May 11, 2012
This is a screenshot of the SotonSocialShare prototype.
SotonSocialShare is a Facebook application and it is shown here working within Facebook.
The menu system is on the left hand side of the screen, when a user clicks their current year the menu is replaced by the modules on which they are enrolled.
A series of ‘portlets’ that the user can move to any configuration they wish, they contain the discussion areas, deadlines and course notes that have been uploaded.
SotonSocialShare is integrated into Facebook, using profile details including profile pictures.
Screenshot of SotonSocialShare
3speech on the World Wide Web
Posted by epan in Front-end Design, Other on May 10, 2012
Since 3speech can only be accessed through the i2p network, we decided to raise awareness of our platform by using a domain in the World Wide Web. The figure below shows a screenshot of the created webpage.
3speech on the World Wide Web
The webpage will also contain details instructions on how to install i2p and reach the community of 3speech.
User Interface Screenshot
Posted by epan in Front-end Design on May 10, 2012
Based on the research on User Interface design and the choice of a navigation scheme, we started building a demo user interface.
First of all, we created the login page of 3speech. This is what we came up with:
3speech – Login page
The page will contain the following manifest:
From now on, it can never be the same as before…because the place we are from does not exist anymore.
The Web is changing, and not for the better. Online freedom of speech is under attack by authorities, corporations and governments. Lobbyists are twisting anti-piracy laws to hide their true intentions and to further their own agendas. Censorship is their weapon of choice and they are trying to utilize it to its fullest extent. They are trying to limit the free flow of information at the cost of your fundamental right to free speech. This cannot be accepted. This should not be accepted.
What we are seeing is only the beginning and things will only get worse. The only solution is to raise awareness and promote open conversations about the issues that matter. 3SPEECH is not the answer, but where the answers can be created.
It is the place where ideas and discussions can take place, allowing its users to remain unaccountable, untraceable and untouchable by current censorship methods.
Talk to your friends, talk to your family, talk to anyone that might be interested.
