I obtained a two-week enterprise account with lastpass and associated that with hcmc@uvic.ca.
I created an ordinary account and associated it with lang06@uvic.ca
I then tried to figure out lang06 could have its own personal information visible only to that account and have information in the enterprise account accessible to it (at least read only).
Their documentation and support is contradictory and confusing on the implications of "linking" accounts. The documentation clearly says the admin of the enterprise account has read/write/delete access to the personal account, but their support person flatly contradicts that. I think there's some confusion around terminology and what is meant by an "enterprise" account vs a "personal" account.
I tried logging in as enterprise account (hcmc) and using the "link personal account" to link to lang06, but that allows only one such linking and is obviously intended to allow an employee to connect their personal lastpass account with their employee last pass account, rather than linking various accounts to one umbrella account.
I then tried creating a shared folder in the enterprise account. I managed to do that and to allow user lang06 to have access to that folder. I could find no indication in the user interface when logged in as lang06 to indicate I had access to a shared folder in hcmc. I was unable to put anything into the shared folder to share, so maybe that's why I saw nothing when logged in as lang06 - though I should have seen a folder even if it had no contents. I'm sure eventually I would have figured that out, but even if I did, I'd then be in the situation where I'd have my real personal account, some bogus enterprise account somehow connected to my real personal account through their "link account" feature and somehow with access to the shared folder in the hcmc account - maybe, and if everything worked out.
That's just getting too complicated. Instead I think I'll create an ordinary FastPass account associated with hcmc@uvic.ca and then give people that need it the necessary information to connect to it.
Forgot to post for last three weeks
week of 24 - Oct 28
M +0.5 hold fort, T +0.5 ENGL 500, W 0, R 0, F +0.5 ENGL 500
week of Oct 31 - Nov 4
M +0.5 hold fort, T +0.5 ENGL 500, W 0, R 0, F +0.5 ENGL 500
week of Nov 7 - Nov 11
M +0.5 hold fort, T 0, W +0.5 hold fort, R 0, F stat
This morning there was a wrinkle getting SK started working on the newly-built Beet machine, which is running Oneiric; I'll detail it here because it may crop up again, and it took me a while to figure it out.
Symptoms: doing an initial SVN checkout of the repo would not work. The terminal challenged the user for a null gnome-keyring password, and whatever password was provided, it then failed to authenticate with the SVN server, and did not provide any opportunity to provide the SVN user name and password. This bug may be related.
Eventually I came upon this solution, which worked:
rm ~/.gnome2/keyrings/login.keyring
We were then able to checkout successfully from SVN using the --username switch.
Finished the minutes, fought my way through the CMS to get them uploaded and working, completed the expenses claim, and mailed it off.
Back on the project for a few weeks, and getting up to speed on developments over the past year. I'm adding this comment of ECH's to the blog for us to think about in the future:
"One thing I wonder about is a glottal stop infix in the middle of a root. Is there any way to make clear that the parts of the root belong together? For example, if a form is ca+?+qw, the root is caqw, but with the tab format you can’t see that."
719 new images (in three different sizes) have been added to the collection. These cover the Vancouver Island 1859-61 Despatches from London.
First day back, lots of catching up to do. While I'm here, these are things I'm not logging -- I'm treating them as personal contributions to the TEI, rather than UVic contributions: two travel days, several hours of G&T arising out of very long work days Nov 9-11, and several hours of follow-up work after the meeting.
Trawling through nearly 700 emails from the last week to make sure there was nothing I'd missed; checking on timesheets and completing one that hadn't been done; discussions around what's been happening while I was away; clearing out three secondary accounts we have some plans for; backing up; etc.
I'm serving on the PDSA Committee again this year, and our first meeting was today. The work starts in a couple of days, and should be done by mid-December.