Hi all,
We have recently been asked to maintain a record of all software purchased by the college on our LMS (Heritage). This is quite a challenge because Heritage does not come equipped with suitable fields built in to the cataloguing module, but we thought that we might be able to doctor some unused fields / tabs so that they are fit for purpose.
Having experimented with a few test records, it looks like we need one area to deal with administration details (for licence compliance) and another for software evaluation (to inform subscription renewals / future software purchases).
Admin details should include things like:
1. Which department purchased the software
2. Where the installation discs and licences are kept
3.Where the software is installed
4. Relevant web addresses
5, Passwords
6. Licence type (single user / multi site etc)
7.Serial Numbers (not visible in OPAC)
8. Licence keys (not visible on OPAC)
9. Time limits on licence
10. Who it can be used by and from where
Evaluation details are likely to include:
1. Date of evaluation
2. Level of student
3. Contents
4. Strengths/Weaknesses
5. Teaching or independent resource?
If we go ahead, this looks to be a massive project. I'm wondering how other institutions are tackling this kind of thing? Have people bought specialist software? Or attempted to incorporate the information into an existing database? If you have had a bash at using your LMS for the task, would you recommend going down this route? How have you managed it? It would be particularly useful to hear from other colleges...and better still anyone who happens to use Heritage.
I'd appreciate peoples thoughts on this and as always, I'd be happy to collate responses and make them available to other lis-linkers.
Suzanne
|