Releasing the metadata prototype

I’m was intending on releasing the first version of the prototype this week, I suspect it will be end of next week now. Came across a few problems. Well the first isn’t really a problem but it is time consuming and must been done right. The question is what Rights package are we going to release the prototype under? Having been to the Web2Rights events and spoken at some length with Naomi from the project I know how critical this is.

So I decided I best go through the process the Web2Rights team have developed and check everything’s in order. First I checked out the diagnostic tool they have developed. As we have developed a new product the process id fairly straight forward. So I downloaded the appropriate checklist. The main things we have to consider are:

• Any third party Library and tool use – this has already been attributed in the code where applicable. Just need to pull out to the top level the CP notices for the libraries I have used.
• Attribute the authors – I’ve assumed I can refer to the project by name rather than the individual members with LeedsMet being named as the lead institution with funding from JISC.
• JISC’s policies – form what I have read they opt for an open source strategy, please correct me ASAP if I’m wrong about this.

Rather than pen our own licence I would suggest using the GNU which according to the information on Web2Rights is compliant with JISC polices. I also suggest going with their General Public License rather than Lesser General Public License for the reasons stated on their information pages .

Now I just have to cut and paste the header into all the code files and problem solved.

Second problem slightly less legal slightly more complex, I’m talking documentation and support. So far I have the help file developed for the recent repository day. This I think needs a bit more detail. I have also hacked the prototype this afternoon so this same doc is available form the help menu.

While talking Tony through the prototype this morning, with a view to evaluation, it was clear from his comments that its not as obvious as I first thought to know what to do with the application. I had intended to do some popup tips for the fields on the edit metadata panels, some are already there. But it is clear that this is not going to be sufficient. I know this is a beta stage prototype, but I think I need to rethink this before we do some serious evaluation.

So I’ve asked Nick and Tony to be guinea pigs to find out which bits critically need some inline help. This is scheduled over the next couple of weeks.

The final thing is name. What are we to call this application? It is an automatic metadata generator, which is a bit long winded and not so catchy. I keep referring to it as the Autogen which really doesn’t say much about it. Suggests on a post card please.