A while ago, I posted about an upcoming exhibition of early modern dresses in Nuremburg. I've since received an update about this - it will start in December 2015. You can read more about the exhibition here.

Also, it's time for me to bleg again...

Together with a colleague, Gillian, whom I met in Leeds, I've been working on a book about medieval England these past years. The book is going to give an overview about England from c 1050 to 1315. We have tried hard to write a book that gives enough detail for those readers who would like to use medieval England as a basis for their own projects - such as a medieval-based fantasy world, or writing a historical novel, or getting started with Living History.

We're now actually in the last stage - copyediting, getting the last few stray bits and pieces in line, and... illustrating it. We have the opportunity of putting pictures into the book, even colour pictures, which is just wonderful. The only drawback? Our deadline is approaching, fast. And we need to get the illustration done double-quick...

A while ago, I've already gotten a few gorgeous pictures for the book, but there are still quite a few topics that are not covered. We would love to have pictures that show actual live persons using good-quality replicas of stuff from England (or non-regional things), from the time-span 11th to very early 14th century. Daily life scenarios, craftspeople doing their work, children playing, any combination of things that actually existed and were used and people using them would be helpful, whether secular, religious, or military. Good pictures of just tools and maybe half-finished products would be very welcome as well.

So... if you have a photo, or several photos, that fit the bill and you would be happy with them being published, please send it to me at Diese E-Mail-Adresse ist vor Spambots geschützt! Zur Anzeige muss JavaScript eingeschaltet sein.. And we will be ever so grateful for your help!

The OA week has provoked some more blogging, not only here. Doug has posted a longish article about OA publishing concepts that sound a lot more reasonable than the ones I ridiculed yesterday. And one before that, with a lot more information about free or affordably-priced OA journals, and links to said journals. Go read it here.

In other news, I'm still busy editing (the Beast is losing words - it's like a book diet!) and also preparing for the Textile Forum. Additionally, I am thinking about offering an embroidery set for doing a small medieval motif, about 4 cm in diameter. I would like to offer that as a complete package with cloth (that has the pre-inked design), naturally dyed silk thread, maybe gold thread, short instructions and possibly also a small (non-medieval, but affordable) embroidery frame. Suggestions as to motifs would be greatly appreciated!

I just found out that this week is Open Access Week. Yes, it's nice and comfy here under my rock, thank you for asking.

I found out, by the way, from an email sent to me by Maney. The email says they are partaking in Open Access Week - and my first reaction was "yay free access to articles!". Turns out that was wrong, though.

The email tells me about the very generous offer of 50% off the fees if you want to publish an article as OA with them. Yes, that's right - Maney is one of the "author pays for OA" journals, and their fees are quite hefty. Even with 50% off, you'll still shell out between 400 and 1000 USD. Erm... thanks, but no thanks. In my universe, the One Rule still stands: the author never pays. Yes, I know that publishers have to eat, too, and that their money does not come from publishing for free and giving away the published articles, too. It comes from selling what they have published - and I still think that it is fair to pay for what you want to read, provided it is not what Germans call a "Mondpreis" (moon price, literally - an astronomical sum that is totally unrealistic). I'm also convinced that a reasonable pricing of articles, especially older ones, would raise their income far enough that a fair-for-everybody model will be possible. (Or would you hesitate for a second to pay one or two dollars for immediate access to a paper that interests you? Instead of being asked to shell out 30+ dollars, even though the article is several years old and you do not know whether it will really help you on with your research, or not?)

You can laugh about the pricing yourself here. Incidentally, the page also offers the full list of OA articles published with Maney. I do not wonder why there are so few... (There is one about spinners and yarn regulation in 1550-1800 that might be of interest to you, too, written by John Styles.)

If you want to read some more, you can go to Paperity, an article aggregator of OA articles. (I found that via www.openaccessweek.org, by the way. The site seems to try for promoting OA, but also seems fairly small, impact-wise, and it has a layout that is a bit confusing to me.)

The Textile Forum is drawing closer and closer, and thus we are busy preparing things and planning. I'm also doing editing work on the book project I am doing together with Gillian - we are reverting some changes that we made during one stage of the project, and both have the impression that our final book will be much better for it. It really is amazing how hard it can be to sort out the best sequence of chapters in a book - and how many bits and pieces would fit into several chapters equally well...

There's even more coming up - I have received hand-woven cloth ordered for the equipment of Lauresham, and it's washed and dried now, ready to be sent off for dyeing. The spinning-wheel tuning is also progressing, though slowly. The next step is a suitably "sticky" drive band to properly turn the whorls on flyer and spool; there is too much slip at the moment, and thus I am not getting the ratios that were planned.

Finally, I am starting to do the lists of things to prepare and to take to the "Kreativ" fair in Stuttgart. It's going to be a full and interesting November!

I've been pointed to a discussion about the journal "Internet Archaeology" by a friendly colleague. The journal IA has recently dropped its paywall and is now free access for everybody - to which I say Hooray and Thank you.

However, as someone in the discussion on Antiquist points out, it's not all free. The journal is financed by an "author pays" scheme, which means you need to be able to pay for having your paper published. The discussion quickly goes off into other terrains where there are problems in data access, but for me, the interesting bit is that one of the contributors says that "author pays" is not a problem, since nobody pays for that out of their own pocket anyways.

To which I say... not true. Definitely not true.

I would never publish in an author pays scheme, not only because I am a firm believer in the principle that the money flows towards the author, not away. I would also not be willing to shell out even more money for an experiment, thankyouverymuch. As a rule, I pay for my experiments myself, because getting funding for them? Difficult. Having an institution behind you makes things easier, but even then it's not guaranteed that you will get funding. Plus the time you have to spend on trying to secure said funding... never underestimate how much of your time, and energy, applications can suck out of your life.

I had plenty of experience with that topic when I tried to secure funding for my phd thesis (hint: I didn't get lucky). You have to do a new application package every time, then it takes ages to go through the system, and finally if you don't get funding, you have to deal with the emotional fallout. (At least I did.) At the end, I estimated about two to three weeks' work worth for each application. There's quite a lot of times that I've heard people complain that they are not getting around to really working, because in order to secure further funding so they will not lose their job, all they have time for is write one grant application after the other.

At some point, especially if the experiment is more work-time and not too much monetary investment for the things you need, you might decide it's not worth the effort to go for funding, and just go ahead and do it. Then, at the end, if all went well, you have an experiment and some results... and there you are. The thing should now be published. The last, very very last thing that I, personally, want to do in that case? Pay the journal.

So who is going to pay the people working at the journal? Actually, I would be fine with a paywall for journal articles - let the reader pay. With one caveat, though: make the prices reasonable. 30 or 50 USD for a 10-page article? You bet that nobody who can get around paying that will pay. However, if you charge 10 or 15 USD - that would be much more reasonable.
And for things that are older than, say, 2 years? If the journals would just charge one or two dollars, you can bet that I would not take the trouble to get the article via the library, or maybe ask a friend who has access. I'd pay, just for the convenience of having it at once. Because it's not a high price, and I'd be comfortable in paying that. Probably a lot of other folks would think exactly the same, and do exactly the same.

Oh, and in my ideal world? The author should get 10% of the income that the article generates. Fair pay for the work that went into it.

Some mornings, even having "Blog" on my to-do list doesn't really help to get you a timely morning blog. I sit down at the computer and then I fall into a hole, doing something and being utterly gobbled up by that.

This morning, for example, I started out checking emails (as usual), writing a few short ones, and then the phone rang. Then I did my Czech lesson. And then had a bit of chat on Trillian for the current book project, and then I thought I'll just do one pomodoro's worth of work on the book right now so that I can send a file over to Australia. Which utterly enthralled me and now I'm in the second hour of work on it, and when taking a short break I suddenly realised that a) the bit of breakfast I had much earlier in the morning was not very much, and b) the blog post is yet unwritten.

So... there's the blog post. Of me telling you why it's late. And because that's not much to blog about, here are some things related to why it's late:

Pomodoro. After a long hiatus in this, I have re-activated the use of pomodoros as productivity aid yesterday. At the moment, it's mostly to make me stick with one subject for at least 25 minutes. It's nice to use this technique again, and it does help - I have gotten quite a bit of work done yesterday and today already.

Czech lesson. I've been at this for two weeks now, and I have the feeling I'm making good progress. Since I'm still quite happy with the programme, I will pass a link on to you. It's from Strokes International; they offer 24 languages (well, 22 if you want the course based in English, and counting English as second language), and you can test the first three lessons for free. They have some of the harder-to-get languages, such as Czech, Polish, Romanian, and you could even learn Japanese.
The programme has the usual problems of a computer language programme with speech recognition - sometimes you need to repeat a word a trillion times, sometimes you don't really know why it won't accept your pronounciation, and there is nobody telling you whether you are really off or whether it's a fluke in the speech recog. Still, it makes you speak a lot. It also makes you write a lot, in a not too nasty way. There are plenty of repetitions, plenty of pictures to help in learning, and a lot of "game-like" exercises such as a memory with the written term on one card, the picture on the other, and you get the spoken word for both as you flip them.
While there are a few small things that irk me (such as having to adjust the window size to my preference every time, and the programme not remembering that I want the keyboard picture at all times), I do enjoy the lessons and have the impression that yes, I am learning stuff, and not just in short-term memory - and that is the most important bit, after all. (I can memorise things quickly and easily for short term, which is nice, but not too helpful when it isn't settled into long-term brain storage, too.) For now, I can recommend it - and I hope it will stay that way!

Collaboration can be a wonderful thing. Collaboration can add new insights, different perspectives, throw up new questions and give answers that one person alone could never have found. Successful collaboration means being able to do something you alone would not be able to do.

Collaboration, if it works well, means less work and less re-inventing of the wheel for everyone involved. More efficiency. Plus the exhilaration that comes with the feeling of, for once, not being alone. Of having someone who pulls the weight with you, that you can carry the load together.

When it goes badly, however, having agreed on a collaboration means nothing but headaches, and heartaches, and the exact opposite of efficiency. There's the added bit of irony that the more a project could profit from collaboration, because each person in the team has expertise and knowledge and a specialty field that has little overlap with the others', the worse it will go and the more heartache it will cause if somebody drops out or does not deliver.

I have had both - the successful collaboration (thanks, colleagues!) and being left alone by drop-outs. It's unfortunate, and bad, and sad, when a collaboration dies. Bad enough when your colleagues tell you straight out that they have to stop working on the project, for a while or forever, because something came up that needs all their time and energy to handle.
It is much worse, though, if you do not get told this. If all of a sudden, communication just... stops, and you feel like you are talking to a wall. With no echo, even. And that is what I hate most about the drop-out thing - the silence. Silence regarding all your mails, all your attempts to get some communication back. You sit there and wonder whether something has happened - an email gone astray, an address going offline, something dire in the life of the other person - or if you really are just ignored, consistently and callously. Because obviously you don't even deserve a short mail saying "I got your mail, things are bad here, please go on without me, sorry."

I know, much too well, that sometimes one bites off more than one can chew. And I believe that either you manage, somehow, to deliver after all - maybe a bit later, maybe a little less elaborate and less brilliant work than your best - or you should own up to not being able to do it. Hell, there's nothing wrong with being honest and saying "sorry, I can't do this now after all". It is unfortunate, and sad, but it is at least some communication and a clear message, and either the project of the collaboration will then die a quiet little death or those remaining in the active team will know that they have to either leave that part of the field untilled or do the work themselves. Letting the others hang, not knowing what goes on? That's unfair.

Having been let hanging rather recently by more than one person, in more than one project, I am not sure when I will do another collaboration. It might be a good while - I am pretty sure, though, that I will not resist the lure forever. For the next time I get into it, though, I will try to remember the following before getting started:

- Make sure you have contact data to reach everyone in your team. Full contact data, as redundant as possible - not just a single email address. Get the full address, at least one alternative email addy if possible, and all phone numbers. You might never need them, and that's fine, but if someone goes MIA - you'll be glad you have them.

- Be clear on communication policies. Also make it clear that whenever in a project that there are problems it will be best for everyone to address these honestly and straightforward - up to and including dropping out or going dormant in the project due to issues of whatever kind.

- Get clear statements on who is in and who is not, and set clear deadlines within the project so everyone will (hopefully) deliver in time.

- Get sorted out, clearly, on who is to do which task, and in what time-frame. Get this communicated to everybody.

- Did I mention getting full contact data? Get full contact data of everybody while they still speak with you. Really.

Unfortunately and as I have learned, even being clear on deadlines and on communication and handing out specific tasks to others is no guarantee at all that things will, indeed, work out. So sadly, but most importantly: Have a Plan B ready for when all this fails, and you are left alone with no communication, no help, and a half-written paper that you don't have the skills, knowledge, or even literature to finish up on your own.

In German, the English term "team" has become pretty much a standard part of our language, and we use it a lot (it's shorter than "Arbeitsgruppe" or something with a similar meaning in German, you see?).
In German, there is also an only half-joking explanation of TEAM as an acronym, standing for "Toll, ein andrer macht's" (Great, someone else will do it). Yes. Well. I think I don't need to say more.