NLindex

A few weeks ago, a brief exchange on twitter highlighted a difficulty common to many fields: how to enable a way in to the literature.
There are lots of ways of providing an index. Google Scholar does some of it. I don't think any of the databases cover the NL conference archive, and we might want to include other non-NLC sources anyway. We have a saying, 'he who has the vision gets the job'.
Joe used Kumu for his Knowledge Hub. Kumu allows for various ways of presenting the same information, so was preferred over CMAPS, as good as that is. Kumu's free for public maps. Anything that requires effort needs to be reasonably durable and Kumu appears to have that. It also has an CSV import, which, data cleaning notwithstanding, could save a lot of time hand-coding. There may be no way to avoid some of that.
Although in lockdown, Alice kindly sent me 3 exports from the SCHED app used in the previous 3 conferences. So, when I can get to it, this presents a viable way forward. It will still require a fair bit of data cleaning and there are some decisions to make... E.g. whether to re-host the papers, where possible. If anyone is interested to help with this project, do get in touch. There could be some bread pudding in it for you...

Compendium 3 CMAP 5

Comparing Compendium and CMAP

• Both offer collaborative visualisation 1-1
• Both have a web-publish option 2-2
• Both are open source 3-3
• Compendium would require admin rights to install at CU unless we wrote a NAL app for it. CMAP is already available on every workstation in the Uni via Networked Apps. 3-4
  
• Compendium stores stuff either on your hard disk or via a MySQL database where CMAP uses a client/server attitude - i.e. sharing is better in CMAP. 3-5

Verdict: I could have gone on but, for my money, while Compendium is nicer to use than CMAP, at my institution, CMAP has the support and architecture where it counts, and it can (with a little coercion - apols to Joe) even be used for Compendium-type stuff.