Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/danpalmer/sussed-mockup

This is what students want from SUSSED.
https://github.com/danpalmer/sussed-mockup

Last synced: 25 days ago
JSON representation

This is what students want from SUSSED.

Awesome Lists containing this project

README 

        
# SUSSED/Intranet Mockup



## [Go to the site ➞](http://danpalmer.github.com/SUSSED-Mockup/mockup/)  

  

*Please* tell me any feedback you have, the only way things you want will get into it is if you *tell us*.



Feedback options:



 - [Github Issues](https://github.com/danpalmer/SUSSED-Mockup/issues)

 - [Email me](mailto:[email protected]?subject=%5BMOCKUP%20FEEDBACK%5D&body=Be%20as%20descriptive%20as%20possible%2C%20any%20features%2C%20suggestions%2C%20problems.%20Please%20keep%20the%20subject%20as%20%5BMOCKUP%20FEEDBACK%5D)



- - -



### What is the Intranet?

Last year the university decided that SUSSED was in need of an overhaul. They did a survey of students (and probably staff as well I assume) to find out what people wanted from the system.



A few weeks ago, as I had responded to that survey, I was invited to the pilot programme for the replacement for SUSSED. For the moment it is called 'Intranet'.



I was disappointed with what I found. Despite being difficult to use and having information in strange places, SUSSED did actually have a large amount of useful information. The new site on the other hand seems to be lacking that. 



### What is wrong with the Intranet?

I think there are 3 main things wrong with the intranet, and from the students I have spoken to so far, this seems to be the general consensus.



1. #### It lacks useful information.

	We mainly want to know information that immediately affects our studies and student life. Our timetable, email, and deadlines are probably the most important things we need.



2. #### It is difficult to use.

	It is quite possible that some of this information we need is in fact on the site. It is just so difficult to use that it discourages us from using it. 



3. #### It doesn't seem to target students.

	I am working on getting more feedback from students on what they want, but so far, the intranet is not it. The direction it is going in seems to suggest a collaboration platform, but I'm not sure that is what students need. Personally, if I need to collaborate on a project, I use Facebook and Google Docs, and I know that a large number of people on my course do the same. These might not be perfect, but everyone checks Facebook regularly so there are rarely issues with contacting people, and Docs has fantastic editing of documents/notes/etc for groups.



### What do we actually need?

These are the primary things we need access to, the information is probably readily available to integrate into the site:



 - Fast access to the information we use most often

 - Email Access

 - Calendar (Events and Timetable)

 - Assignments/Deadlines*

 - University News and Announcements

 - Course and Module Announcements*



These are the secondary things that some people may like access to. The information may or may not be readily available, much of it may be in systems like Scientia:



 - Room Bookings

 - Directory/Person Search

 - Don't optimise it for IE, no one uses it.



`*` This may be out of the scope of the system



- - -



### Contributing to the mockup

Fork this, make changes, submit pull requests as usual, but try and stick to the following guidelines:



 - This is static only, and should remain so.

 - Any new pages you integrate, make sure they are accessible from the index page, link in the way they would be linked properly, or in the footer if you have to.

 - Stick to the current design, use Twitter Bootstrap where you can because it's awesome and makes a consistent UI.