Showing posts with label CMS. Show all posts
Showing posts with label CMS. Show all posts

Friday, June 22, 2012

Last Day at the Museum of the History of Science

MHS banner from Winter 2010-11 advertising a 360 degree panoramic tour

Engraving of the East Front of the Museum by Michael Burghers, 1685Today was officially my last day as Web Officer at the Museum of the History of Science in Oxford, which has the distinction of being housed in the world’s oldest surviving purpose-built museum building, the Old Ashmolean, an early impression of which is as right.

I had the pleasure of working there since October 2009 with a close-knit group of dedicated, friendly and enthusiastic staff with a wide range of interesting backgrounds. So I was sad to leave and surprised how difficult it was to hand in my keys and especially the University card - I felt quite bereft as though I had lost part of my identity.

I found the Web Officer role similar in many ways to a previous one where I was responsible for anything Web-related; it requires some flexibility as the duties are varied, ranging from system administration (at the command line) and documentation through to some elements of graphic design, particularly image composition. In summary I would characterise much of the effort as consolidation - in terms of the Linux-based hosting provision, and the use of WordPress as the gateway to the entire online presence.

WordPress gets used mainly for blogging, albeit with resources built around it, but at MHS it is used as a content management system. Perhaps the most significant development was the integration of the KE EMu collections management system, for which I prepared the following slide for the 2011 KE EMu User group meeting, held at the Natural History Museum.
A lot of the work was behind the scenes. A particular challenge was search engine optimisation (SEO); it took me a long time to realize that a WP upgrade had inserted canonical URLs into the header, leading to just a handful of collections pages being indexed. Once I had removed that and made the page titles more distinct the index grew and more visitors came.

Just occasionally I could do something a little different. For instance, when faced with slightly blurred image, I suddenly realized an opportunity to create an inverted reflection in time for the somewhat wacky and hugely successful Steampunk exhibition:

Steampunk Live Mannequin
(I manually traced the figure; some regions have little contrast so I suspect an automated tool would probably struggle)

The old uniform is brought into the present, whilst the photographers (who strive to capture the present moment) recede into the background, into the past, by being faded to grey.

Now too my fleeting role as Web Officer will start to become a faded memory. However, I'm not leaving the museums world, as soon I shall start another role, supporting not one but many museums ...

Friday, October 01, 2010

Installing MySource Matrix on a Win XP Netbook (for evaluation)

Among the crop of open source content management systems that are deployed at Oxford, I recently had my first encounter with MySource Matrix, developed by Squiz, which is released under GPL. I decided to take a closer look by installing it on a netbook running Windows XP Home, just to have a poke around. The official requirements are a UNIX-like operating system, but this is a Web application, so in principle I think it ought to work, just as I can be confident in installing WordPress or Drupal. This should be the case, even though MySource Matrix is definitely a more substantial proposition in that a default install seems to gives you 'the kitchen sink'. The following is a screenshot after I had created my first page:

screenshot: MySource Matrix admin panel

As I couldn't find anyone else writing about it I thought I'd share an outline of the process I went through in case others would like to evaluate on this platform. I apologize in advance for not offering any support or follow-ups because I've since moved on/back to other systems for now, so for queries I think the best place would be the support forums.

Requirements

I carried out the installation at the beginning of September 2010, mainly following the steps in the installation guide provided by Squiz. The first thing that I'd stress is that it doesn't support the latest version of PHP. I really should have read the requirements more carefully as I did try 5.3.x and progressed only so far until I hit an issue reported on the forum. Afterwards I dropped back to version 5.2.14.

For the Web server I am running Apache 2.2 and this appears to be the recommended choice for working with the other components.

For the database back-end, MySQL is not supported, but there is a Windows distribution of the freely available PostgreSQL.

Installation

Apache (preliminary): A standard install should be fine as a basis to work with installing PHP and its libraries. For the Matrix config itself, see later.

PostgreSQL: For reference, I used Squiz's page on database installation. I installed Postgres 8.4.x using the Windows easy installer, accepting the defaults. Then for the installation of the Squiz database I used pgadmin, specifically pgAdmin III (v. 1.10.3). From the command line I issued the following commands to create two users: $ createuser -SRDU postgres matrix
$ createuser -SRDU postgres matrix_secondary
where -S: NOT a superuser, -R NOT allowed to create roles, -D NOT allowed to create databases, -U connect as username.

Then I created the database: $ createdb -U postgres -O matrix -E SQL_ASCII mysource_matrix, where -O owner, -E encoding. Note that it's important that the right template database is used — template0.

Comment: pgAdmin warns that storing data using the SQL_ASCII encoding means that the encoding is defined for 7 bit characters only. So it is dependent on the Web application to do the conversions (since content served to the Web is typically 8 bit UTF. I wonder if this is an indication of the longevity of the software...?

At some stage, you need to create the PLPGSQL language for Matrix. I did this in pgAdmin once I had run from the command line: C:\PostgreSQL\8.4\bin>createlang.exe -U postgres -d mysource_matrix plpgsql, but for a while I had some difficulties and needed some guidance.

PHP: When installing PHP (I did this via the MSI installer), I did the custom configuration to ensure support for PDO. There are other bits, like SMTP support, that should be included also, but selecting everything is not a good idea because, for instance, it will then expect that an Oracle client is installed. The most immportant of these is the PEAR Package Manager since MySource Matrix depends a lot on the additional PHP libraries that PEAR provides.

I actually did the PEAR installation separate from the main PHP installation, by running the gopear.php script from within a browser and subsequently installing packages through its Web front end. A lot of modules are needed and I'm not sure that my list is complete, but for what it's worth, here is a list of what I've installed so far from the channel pear.php.net: Archive_Tar, Auth_SASL, Cache_Lite, Config 1.10.11, Console_Getopt, HTML_Template_IT, HTTP, HTTP_Client, HTTP_Request, I18N, Image_Canvas, Image_Color, MIME_Type, Mail, Mail_Mime, Mail_Queue, Mail_mimeDecode, Math_BigInteger, Math_Stats, Net_SMTP, Net_Socket, Net_URL, Numbers_Roman, Numbers_Words, PEAR, PEAR_Frontend_Web, Structures_Graph, Text_Diff, Text_Highlighter, XML_HTMLSax, XML_Parser, XML_RPC, XML_Tree. Note that all these are marked 'stable' apart from Image_Canvas (alpha); Numbers_Words and PEAR_Frontend_Web (beta).

Basic Config Settings

With everything in place, I was ready to run the php install scripts. Here I emphasize that the PHP PDO and PDO_PGSQL modules must be installed for this to complete. For step 2, you need to ensure that there is the right access to Postgres. by editing pg_hba.conf to have lines roughly like:

host    all         all         your_local_IP/24          trust

Then at the end of running the script it should report at end: all secondary and tertiary user permissions fixed.

For step 3 I found I needed to specify a locale like: C:\www\home\websites\mysource_matrix>c:\PHP\php.exe install\compile_locale.php c:\www\home\websites\mysource_matrix --locale=en.

Apache (config for Matrix): a virtual host needs to be created, which for my setup of Apache is in conf/extra/httpd-vhosts.conf. I created a named virtual host for Matrix with the lines:

  NameVirtualHost site1.local
  NameVirtualHost 127.0.0.1
(apparently using localhost won't be sufficient).

The installation directories are a matter of personal preference, but as I could see some long directory paths, I've set the Matrix Home directory to C:/www/home/. This allows a fairly close following of the suggested config for UNIX, though file paths still need to be edited to cater for Windows directories. The relevant virtual container starts:

<VirtualHost 127.0.0.1>
 ServerName site1.local
 DocumentRoot "C:/www/home/websites/mysource_matrix/core/web"
 Options -Indexes FollowSymLinks

I also found that I needed to insert another alias into the Apache httpd.conf for asset_types: Alias /asset_types "C:/www/home/websites/mysource_matrix/data/public/asset_types" Alias / "C:/www/home/websites/mysource_matrix/core/web/index.php/"

I then followed a quick start guide and was able to complete the steps there.

Conclusion

Not a 5 minute install like WordPress, but it is fairly straightforward, at least in hindsight!

Sunday, July 15, 2007

The Quest for Sustainability in Open Courseware


Note: This article was originally posted in the Connect section on the Educause Web site, at:
http://connect.educause.edu/blog/pault/thequestforsustainability/44767. 
However, this address has since become inaccessible, so the post has been reproduced here as an archive with the same date and approximately the same time.


I've been reflecting recently on the subject of open courseware and, more specifically, OpenCourseWare following the keynote for the Sakai conference in Amsterdam delivered confidently and enthusiastically by Hal Abelson (a podcast is available). In this post I'll briefly recap some of the core aspects as I understand them and then go on to explore this area, based on personal experiences and ideas I've been formulating at Oxford.

Abelson took a broad view, inviting the audience to go back 25 years and defined programming as a "novel formal medium for expressing ideas." Against that, he got us to consider the aspirations and expectations that we might have had then, encapsulating this in 3 predictions for 25 years thence (i.e. today):
  • a global encyclopaedia
  • TCP/IP global
  • collaborative educational resources
It's the third that has yet to be properly delivered. Starting from consideration of why not, he then developed the rationale leading to the MIT OpenCourseWare (OCW) initiative and the more recent Creative Commons Learn (ccLearn).

Abelson described OCW and ccLearn as means to building infrastructure for sharing academic pursuits, covering platforms and materials in Sakai, policy structure and media structure, designed in such a way as to protect academic values. The need to beware certain kinds of commercial activities was drilled into the audience: such concerns are, he argued, keen on monopolising and overcharging us. So, in the face of impending monopoly, it was argued that we need OCW, shared repositories etc, in order to be taken seriously at national and international levels. The IPR issue highlights a tension between the commercial and academic world. He urged everyone that we shouldn't leave it to the publishers to control, and by way of illustration mentioned that universities can have a policy on publication that insists on the right to retain rights and publishers should be sought that allow reasonable IPR.

Enter Creative Commons' ccLearn:


Our goal is to make material more "interoperable," to speed up the virtuous cycle of use, experimentation and reuse, to spread the word about the value of open educational content, and to change the culture of repositories to one focused on "helping build a usable network of content worldwide" rather than "helping build the stuff on our site.

It's new to me and one month on I've subsequently tried to find out more. I certainly haven't searched far, but ccLearn still seems largely hidden, with little information available: someone who hears about it might well type cclearn in Google and would find cclearn.com, the 'Center for Creative Learning,' which has also taken the domain cclearn.org. I found it difficult to come across much of substance regarding ccLearn - just a few snippets, e.g. a mention on Stanford's Center for Internet and Society. Of course, as it's a Creative Commons project, you could go to the creativecommons.org site, but when I entered cclearn site:creativecommons.org in Google only one match was returned! At least it informs us that they now have an Executive Director - Ahrash N. Bissell - congratulations to him :-)

The presentation itself flowed swiftly with ease until ... there was a big anticlimax at the end when the economic realities became evident - in Q&A at the end he admitted that the average cost of preparing an MIT course the OCW way is around $15,000-$20,000, mainly down to legal concerns apparently.

Indeed in a subsequent session, 'Open courseware, pedagogy , Social Practices and Tools,' which elaborated on OCW initiatives, major problems with the current OCW were identified:
  • too expensive to create OCW sites
  • little or no automation
  • no connection to CLE
  • only large institutional commitment can get OCW off the ground
OCW is a meritorious activity and undoubtedly makes a major contribution to making more visible the academic enterprise - the Webometrics 'World University Rankings' provide some indication of this with MIT sitting on top of the table (whereas Oxford lies many places beneath). It can be argued that these are very limited measures, but Web visibility really does count.

Given that it's worthwhile, but costly, how might there be economic sustainability? One might look for inspiration to open source software (OSS) generally and follow the example of seeking revenue from support, certification etc., but I expect this has already been covered. More specific to the educational context, the Open courseware session expressed the hope that the next generation of OCW, dubbed OCW2, will reduce cost by employing graduate students, trained to understand licensing, and enabling them to share in the academic sphere. To enable this, they are looking at incentive structures, trying to get early buy in. The graduate helpers are called Digital Scribes whose engagement can work positively to foster "co-creation" and "communities," but I think graduates may well swap and change how they earn enough to get by, so can't always be depended on. We also heard that from another point of view, OCW may be regarded as filling out the long tail of publishing (a phrase coined by Chris Anderson), as illustrated by Amazon, which is able to sell at least one copy of every book, no matter how obscure, thus offering a chance to support specialisms (J.R. Hartley would be pleased!) and I guess Lulu is another good illustration. However, overall, I'm not convinced this will be much better.

So what would this small person from a small island suggest as an alternative approach?

Allow me to start with a quote from one of last year's extraordinary debates on the governance of Oxford University. It comes from Donald Fraser, Professor of Earth Sciences, who as reported in proceedings from Congregation , 14 November, 2006 stated:
Dynamic knowledge-based businesses are moving away from large, centrally administered monoliths, towards small, self-organising entrepreneurial cells, flexibly connected and practically self determining—just look at the campus models of companies like 3M, Google and Apple.

What does that mean to me as someone who works in academic support? The message I read (and readily agree with) is that academics rather than administrators are the ones who, along with their colleagues and peers, are in the best position to determine what they should do with their academic activities - in terms of how it can help them, their department, their field of study and their students. In the context of the debate as a whole, he was arguing against the motion because it contained proposals that were seen as increasing central control over the academics in ways that would threaten their independence and autonomy. From this, I infer that essentially that academic endeavour starts internally and is facilitated by an inter-networking mode of operation. If you look at the origin and flow of ideas, it often starts wthin one individual, spreads to a group and then more widely. It's a fact not just of research, but of teaching and of any other activity. Institutions need to support this as best they can, particularly as individuals are becoming increasingly mobile, moving from one institution to another.

This view of academic freedom doesn't deny the institution and its overall mission, but it does ask for a light touch, in terms of how academic enterprise is directed and also in terms of general bureacracy, particularly the legal aspects. I guess this is one of the major issues of OCW and I wonder if OCW2 really lessens this. I think a basic lesson to take from the governance debate (I'm not sure I could grapple with many of the subtleties) is that we should seek first to clarify principles: the professor is the academic authority who should drive the decision-making subject to the authorisation of the institution. In order for this to work effectively, the authorisation should be devolved, which is actually the traditional way in which Oxford works. If it's not suitably devolved, then you get a lot of overhead, so that institutional approval becomes necessary for very small steps, making things very expensive.

Such a devolved view can then transfer much of the responsibility to individuals, requring them to focus especially on basically two main issues:
  • appropriate use of content that you haven't produced yourself
  • deciding on the rights you wish to grant to content you have produced
If these issues are addressed as early as possible in the course creation lifecycle - by determining what's needed in the way of permissions and what should be granted in the way of rights - then that should save a lot of resources later on. With the right training, by the time materials are published the first time in a course management system, the main licensing issues and policy should already be resolved so that when it comes to making available as open courseware, the main effort is technical. This is dependent, I think, on authorisation at the highest level established as early as possible, ideally at the outset, so that it is quickly devolved. The kinds of authorisation I have in mind is a policy document on the kinds of licensing that are permitted, how the University is identified with each publication, specifically giving academic members the rights to publish according to Creative Commons licenses subject to various terms and conditions. Gaining authorisation itself may not be easy, though, as the institution will likely require strong arguments as to the benefits of making content free to use and repurpose - ICT staff may already have had a taste of this in trying to persuade their institutions to let them release software under an open source license.

Assuming processes can be put in place, what does this mean for implementation?

The OCW presentations I've attended have conveyed the sense that OCW is a long way from just open educational content - I certainly got that impression from the Educause '06 presentation Open Sharing, Global Benefits - The OCW consortium where open educational resources - were defined in terms of digitised materials offered freely and openly to use and reuse for teaching, learning and research; whereas open courseware are specific kind of educational resource materials, which have to be organised around a course, though the duration is open. There's a lot of emphasis on process and, in particular, OCW requires that content must be IP-cleared: every contribution gets passed through and checked - sometimes it is removed or replaced where it is felt that copyright has not been granted on at least some content. When I stepped back to reflect on openness in open courseware, I could see quite a few severe hurdles to surmount, some of which seemed unnecessary. Such a heavyweight approach has led to some consideration of sustainability in terms of a few institutions managing the processes, hosting OCW content, and selling this as a service: Wolfgang Greller sees this is an opportunity for OpenLearn, the OU's version of OCW.

However, I have reservations about the hosting provision at such institutional level through third parties and, in any case, my view is that we are dealing essentially with another output, one that results from existing internal processes to which most resources have already been devoted. Rather, institutional ownership can be expressed naturally through their own LMS, which can provide many organisational benefits, not least a single point of access to all study resources for students and for external examiners. However, If we are to support academics individually as originators of content, then the LMS system needs to support personalisation, a flexible environment in which to organise and publish. Indeed, I feel that the way Oxford is run in a devolved and self-organising way points to more organic and sustainable means that make sense particularly with the host of Web2.0 technologies are available. Hence, I now feel more confident that an LMS can provide valid linkage between personalisation and open courseware, as intimated in my poster at last year's conference in Dallas.

I think we should try to envision how it would work for an academic. I imagine a Professor accessing a LMS and going straight to their personal area, in which they have inter alia options to create, review and share content. For Oxford users it means using MyWebLearn, which makes available all the tools necessary to author a course. Sharing the material can be carried out literally in a few steps:
  1. Log in.
  2. Go to the resource you wish to make public
  3. Click on the link 'View Access' at the bottom of the page.
  4. In the following page go to the pull-down menu 'Allow..' and select 'Public' to 'look at' this page.
  5. Click on the [Add] button to enact.
This simple mechanism has already been used to some extent in WebLearn, evident in Google with a few thousand resources (pages) indexed compared with fewer than a hundred pages from another institutional VLE with the same name! However, this process only enables the materials to be put in the open. From the academic's perspective, there needs to be added to this the means for specifying the licensing. Assuming a suitable policy and process were in place, then options could easily be added. Overall it needs to be very easy to use, ideally as easy as contributing to a blog.

On the other side of the coin, materials published this way as courses need to satisfy certain organisational and structural requirements - the content should be sourced from departmental areas, which need to be planned and designed into the system. Also, to be discoverable they need to be indexed with suitable metadata; and interfaces need to be provided that pull together all the relevant information in a meaningful way. We can achieve this by mapping to institutional structures, e.g. the LMS can automatically insert meta data about department, so that subsequently presenting the courses on offer as a whole, can be achieved by aggregation, say. Here I think we can learn from Warwick blogs, an institutional blog hosting service in which staff and students are able to write freely and connect with others. However, they have linked in with their institutional NDS LDAP directory, so that you can browse blogs based on department and even module of study. WebLearn already uses the institutional map in that it is hierarchical in structure, with the top two levels controlled centrally as far as departments and colleges. However, once at that level, areas are managed locally, i.e. content creation has been decrentralised, allowing natural growth.

The issue of quality control should already be handled in the processes of preparing the courses at the institution; what is being provided is largely a snapshot of the materials that were used in live courses. Whatever the processes, I think it is important that the decisions about releasing such content are devolved as much as possible and that the mechanisms for effecting it are as easy as the illustration above. I understand that for OCW(2) processes are being developed for Sakai to make publication a smoother process, so perhaps the production of Creative Commons licensed content may be an option in future, though I wonder how devolved it is and whether it revolves around MyWorkspace. Also, until Sakai has hierarchy, in comparison the technicalities of generating such materials appear far easier in Bodington (and I suspect developing pipeline processes to go with them might be easier also).

If another editorial layer is needed, then that can emerge from peer networks. A number of years ago I came across the Hippias search engine, a service (now merged with Noesis) that as I recall had an editorial board of experts in Philosophy whose members each maintained their own Web sites. These sites contained links to other sites and the Hippias search engine would index all the pages at the end of these links, thereby building a trusted indexed collection. I think it's a very apposite illustration of how you can combine devolved human quality control with automation.

This is obviously work in progress and much is still open to debate, but from the view I've described above, I think the focus should very much be with the academics, devolving much of the decision-making and supporting them as appropriate. Technically, this means Web2.0-like approaches should be incorporated and so I expect many elements of ccLearn could play a major role in facilitating institution-oriented OCW.
I hope to talk more about personalisation and Web 2.0 in future posts...