Melodeon.net Forums
Discussions => General Discussion => Topic started by: Martin J on August 25, 2008, 01:55:13 PM
-
This Q has probably been asked before but is there site which shows all the old models and their details.
I often have trouble locating certain models and end up doing google searches etc. No point in reinventing the wheel if a site exists with all the details. Perhaps they should be on this site ? We have Makers - limited and keyboard layouts, also limited. What about a History section with full details of every maker and model ? The Hohner section alone would be very large.
-
Hi Martin
That is a great idea, but unlikely to happen unless someone (you?) volunteers to take it on. It could turn out to be a big task, and would require continual maintenance as makers change what they offer. But if you are up for doing it you will be helping a lot of people.
-
Martin,
The Hohner section alone would be ginormous! (Considering all the different models they've built in their own right since they started making accordions in 1903, and all their sub-brands, and ones made specially for distributors.) It's mind-boggling... :o
However, I've been collecting old catalogues (pre-1955) for a while now, and can put a fairly accurate date on many of the older models, whilst for dating features of some of the more recent ones, I'd recommend taking a look at this thread on ReyesAccordions.com: Hohner Corona old/new style (http://www.websitetoolbox.com/tool/post/gilbert27/vpost?id=886286)
-
Wow, no wonder I've had limited success in tracking down certain models. Your link (triskel) is mind blowing in the detail changes that go on over the years.
My immediate reaction to Theo's confidence is that such a project would need to be automated in a database. Whilst I can help with specifying the fields structure and links I am no programmer. I'm sure we have members who are and can recommend a framework which would house such a project. I believe this forum is a similar tool, ie. an off the shelf forum tailorable to the users need. My apologies if it is a one off application.
My view is that an instrument database would need to be along the lines of Wikipedia allowing members and manufactures to update and advise of models/marks etc. Having never used Wikipedia I believe the concept is good but the implementation can lead to serious errors if news reports are anything to go by. Within Melodeon.net errors may well be caught rapidly and corrected.
Along with other members I could immediately fill in the details of my own instruments. This would get the database off to an amazing start. I too have old catalogues going back to the 80's and an odd pamphlet from the 50's. Once the database reaches 'critical mass' manufacturers will be keen to ensure that are fully and correctly represented. All great stuff for research etc.
Still, there may already be such a resource. Over the next few days maybe someone will give a URL or build on the idea that is hatching here.
At a very primitive level a word processor could be used with a page per item and a very large index. Programmers please throw your hands up in horror and put me right.
-
At a very primitive level a word processor could be used with a page per item and a very large index. Programmers please throw your hands up in horror and put me right.
It is easy to implement a database with a web front end. That could be done on a weekend. But first you have to determine, what you want to put in the records: Manufacturer, years of production, minor variants, antecessor, successor model, pictures, ...
After the structure is defined, it is easy to realise it, using for example MySQL and PHP.
Amicalmen,
Sebastian
PS: I would prefer not to have to transform word processor documents... ;)
-
That sort of thing would be extremely useful. I've just bought a Hohner Club 1B (http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&rd=1&item=330261685879&ssPageName=STRK:MEWA:IT&ih=014) on German Ebay, and asked for it to be delivered to my daughter in Düsseldorf. I've searched for any information on the web to try to find the dimensions with no joy. I'm sure I've found a site with that sort of info in the past, but not this time.
-
Same style 11B Victoria is approx 320x310x190 mm and weighs in just under 4 kilo
-
Just like that! Thank you.
-
I don't know if this is what you are looking for, but this website lists many makers. It seems that it was taken from other people's pre-existing lists, but giving them credit as to where the information came from. It might be woth checking out. http://www.accordionlinks.com/manufacturer.cfm#manufacturers-parts (http://www.accordionlinks.com/manufacturer.cfm#manufacturers-parts)
-
You may glean some model history from Canadian, Ray LaForest.
http://raymond.antonakos.ca/Accordion_History.htm (http://raymond.antonakos.ca/Accordion_History.htm).
He has attempted a history of the accordion/melodeon on his site.
He has a collection of about 250 accordions, photographed and dated.
You may not agree entirely with his identifications but his life and playing
career make a good read. A site well worth a look at.
John
-
My view is that an instrument database would need to be along the lines of Wikipedia allowing members and manufactures to update and advise of models/marks etc. Having never used Wikipedia I believe the concept is good but the implementation can lead to serious errors if news reports are anything to go by. Within Melodeon.net errors may well be caught rapidly and corrected.
There are plenty of free scripts to do the job such as mediawiki (http://www.mediawiki.org/wiki/MediaWiki) that are fairly simple to set up if you have a server with php and mySQL. You would then have your own "mini-wikipedia" which you could load with the information on makers and their products. Its much more flexible that way than constructing a bare database and choosing the required fields, setting up searches etc. and could be installed in much less that a weekend.
But the big but is the huge amount of time it would take to collect and enter all the details. As I asked before - do you want to volunteer to do the research?
-
You would then have your own "mini-wikipedia" which you could load with the information on makers and their products. Its much more flexible that way than constructing a bare database and choosing the required fields, setting up searches etc. and could be installed in much less that a weekend.
Yes. (Well, of course technically a wiki is just a database.)
On the other hand it is difficult to structure the content of a wiki and to search for specific attributes.
But the big but is the huge amount of time it would take to collect and enter all the details.
Yes. :)
Sebastian
-
Hi Theo and Sebastian
I'll respond to Sebastian first if I may. I'm not a techi so; do I understand correctly that a 'wiki' is perhaps not the best vehicle to house an historic database ? And secondly, I take your yes as agreeing with Theo regarding the amount of time.
This brings me to the non techi question of about 'wiki'. I thought the information was entered by the visitors. I envisage that if Bill had asked his question then 'Shytalk' could have entered everything he/she knew about the model, starting a new record if it didn't already exist and then let Bill know the database had been updated. The record would have been in the Hohner section under Club and then the various marks and types of that instrument. This way the database becomes self generating.
I'm not dodging your question Theo but at this stage am trying to establish the size of the problem and the time commitment required which you have indicated will be a lot. I would be naive to jump in with my limited knowledge of the methodology.
Back to Sebastian. My first thought was a simple flat database where virtually the only search criteria was to be the make and model, once you reached that record the various marks and history for that instrument would be within the record. Is this over simplistic ? What would people really like to search for ? Perhaps other members will respond with what they feel is the basic criteria for an historic database and what use they would get from it, indeed is it even wanted ? Manufacturers, if you read this site, what would you want ?
I realise that maybe a survey would be needed before building something useful but right now polling opinions should identify if it's worth pursuing or if it's just a pipe dream.
-
Martin
I think its definitely worth pursuing the idea. But to give a small example of the amount of detail needed:
In 2004 Hohner published a list in their book "History Unfolds", published to celebrate their 100th anniversary of box production. It lists approximately 450 models, and its incomplete! It does include piano accordions too, but even so it gives you an idea of the order of magnitude. Another complicating factor with Hohner is that they produced many variants of each model, and in many cases used different names for what is essentially the same model, and also used the same name for completely different models! For example I have a Hohner "Mein Leibling" which is an identical model to the Preciosa, just to add to the fun their is also a Hohner harmonica named Preciosa. "Picoletta" was used as the name of an early Club model in the 1920s/30s and also for a small piano accordion in the 1950s/60s.
Then there are all the Saxony makers who between them used dozens of brand and model names, including models produced and branded with the name of a shop. And then there are the Italian, Swiss, Austrian, Estonian, Finnish, French, US etc etc makers
As I said I don't to put you or anyone off taking this on, but its best to know what you are getting into. To have a reasonable chance of success I believe this needs to be a collaborative project, and using a Wiki gives the tools to do that. It could even be done as a topic within Wikipedia.
-
It lists approximately 450 models, and its incomplete!
Theo,
I'm afraid I'd go further, and say it's very incomplete. :(
Then there are all the Saxony makers who between them used dozens of brand and model names, including models produced and branded with the name of a shop.
I'd suggest there have been at least many hundreds, and maybe thousands, of possibilities from Saxony, if you want to cover all the brand and model names.
I can give you a list of 59 makers from one corner of that region alone! And I don't believe anybody knows "all the makers that ever there were".
Like I said, it's mind-boggling... :o
-
There is no contradiction between "wiki" and "database". A database is just the technic behind the wiki front-end. A wiki is just a set of database + web front-end. Everything in a wiki is stored in a database.
Yes, I believe the "wiki aproach" is very helpfull: everybody can change and add information in a simple, straight forward way. But maybe it would be helpfull too, to specialise the normal wiki layout, so that there is not one big page, but different fields for "maker", "brand", "year(s) of production" &c.
While a normal wiki setup enables great freedom in presentation and organisation of a single record, it may have limitations in structured searching. How, for example, will it be possible in a wiki to generate an overview of the temporal progression of the models of a specific maker? Or of the models, a specific maker offered in a specific space of time? Or, if only concrete, palpable instruments are included, it would be interesting, to generate a statistical overview of the chronological distribution of these instruments. Etc. pp.
But maybe those statistical overviews may not be needed. ;)
Nevertheless, the technical questions are not essential. I agree with Theo that the real problem is the data to feed the system with.
Amicalmen
Sebastian
-
Still in the ‘finding out’ stage I have constructed a fields list for the proposed database. As a first draft I know others will want to add (or remove) fields they feel are important or redundant, but here goes.
Field Type of Field
Record ID Numeric
Manufacturer General
Model Name General
Model Mark General
First Made Date
Last Made Date
Associated marks General ie. Other brandings
No of Treble Buttons Numeric
No of rows General
No of treble reeds Numeric
No of treble registers Numeric
No of bass Buttons Numeric
No of bass reeds Numeric
No of bass registers Numeric
Type of reeds General ie. Tipo mano etc
Original Tuning General ie. Swing, Tremolo etc
Case General ie. Wood. perloid etc
Height Numeric
Width Numeric
Depth Numeric
Weight Numeric
Picture Field for 6 images
(Bugger, still can't make a table work - I may have better luck with a relational database)
The associated brands field may be able to hyperlink to any mentioned model within it. There should probably also be fields to identify sources, last update, who verified etc but I think simple is possibly best.
Once a format can be agreed then some of our computer literate members can probably advise the implementation and how on earth in can run within Melodeon.net ?
Sebastian, you are way over my head - temporal places are where I go to enjoy pre prandial cocktails without being baked by the Sahara sun and my reed wax melting. But, have I misunderstood the last item 'data to feed the system with'. Surely this comes from the members as an ongoing living and growing database as people add their combined knowledge. One person couldn't possible feed in all the data gleaned from members, it has to be automated. Perhaps liaison with a major manufacturer such as Hohner would dictate the database fields so that information from them could be directly dropped in ??
Thanks everyone for the input, I'm still hopeful. I understand your point Theo regarding the Hohner book but publishers are limited by the number of pages an able bodied person can reasonably be expected to lift, world pulp production and the amount of coin they can extract for their efforts whereas a cyberspace book can be fairly limitless. As to the multiple use of the same name I have many times found myself looking at mouth organs and melodicas having searched for a box so a cunning algorithm will be called for at the construction stage to minimise confussion.
Lastly, Rome wasn't built in a day but they didn't have an on line forum or Theo as the foreman ! :)
-
Field Type of Field
Nice list. It would be possible to add any number of pictures, so it has not to be restricted to six.
I would want to add a possibility for "notes/remarks".
Sebastian, you are way over my head - temporal places are where I go to enjoy pre prandial cocktails without being baked by the Sahara sun and my reed wax melting. But, have I misunderstood the last item 'data to feed the system with'. Surely this comes from the members as an ongoing living and growing database as people add their combined knowledge. One person couldn't possible feed in all the data gleaned from members, it has to be automated.
Sorry, for the past 25 years I hoped my English would improve -- but I'm still hopefull. ;D
Yes, you are right of course. The appearance should be wiki-like, so that everybody may add and correct the content.
Amicalmen
Sebastian
-
It would be interesting to add a field (or perhaps a suggestion for the comments field?) that records the tradition for which the instrument was designed, and the tradition(s) in which it is commonly used, or the best guess of the contributor in these categories. That would allow for some interesting cross-tabulation between, say, the 1.5 rows used by the organetto folks, the 1.5 rows used by the American Irish folks, and the 1.5 rows just rolled out by the Quebec folks.
-
Thanks Mathew, I certainly would have liked to know all of that a few weeks ago having just taken delivery of fantastic Giustozzi 1.5 row but I am now very disappointed with the heavy Italian musette which I will have re tuned to be sweeter to my ear. This is the first box I have ever bought unheard. I had listened on Youtube but mine is in G and growls at the low end. It's no reflection on Giustozzi, the box is first class.
I will certainly add your fields to the database along with a remarks field as suggested by Sebastian.
I'll wait for a little more feedback before compiling a new fields list.
Q for Theo. You suggested it may even be a topic for Wikipedia. Can you see anyway in could be an integral part of Melodeon.net ?
I am undecided on which is best. Melodeon.net members will be very careful over accuracy and it would only be members who could update whereas in the open sea of Wikipedia the wide band of knowledge may be offset by 'I think I know brigade' and the malicious. (I don't know how the site is protected from rubbish entries) I feel it will be a valuable resource by the members for the members which outsiders are welcome to view but not alter without joining and being known to you in some way.
-
It would be possible to add any number of pictures, so it has not to be restricted to six.
I don't where the database is to be located but images are not disk-storage friendly and come in 57 varieties - tif,bmf,jpg etc
-
There's a document on the Hohner site: Hohner Akkordeon Modelle (http://www.hohner.eu/upload/links/l_00000558_Hohner%20Akkordeon%20Modelle%2006_2006.pdf), which has a lot of possibly useful info.
I had a look at the documentation for MediaWiki (http://www.mediawiki.org/wiki/MediaWiki). It looks complicated enough without trying to shoehorn another data model on top. Would it be possible to use something like a template for new pages, possibly partially filled in according to context, so that users can just fill in the blanks? If a particular make or model warrants additional info, it can just be added.
-
Q for Theo. You suggested it may even be a topic for Wikipedia. Can you see anyway in could be an integral part of Melodeon.net ?
I am undecided on which is best. Melodeon.net members will be very careful over accuracy and it would only be members who could update whereas in the open sea of Wikipedia the wide band of knowledge may be offset by 'I think I know brigade' and the malicious.
But I still think that all this detailed discussion of database structures is putting the cart before the horse. The first step should be to make some sensible estimates of the amount of information you need to collect, what are the sources, and who will have enough time to collect it.
I imagine there will be quite a lot of material that will be fairly easy to get hold of, such as the stuff Hohner published in 2003, and makers websites will give some information about the bigger factories current offerings, but where will you get the huge bulk of information on instruments made over the past century and a half? The only way I can see of doing it is to spend many hours visiting museums, libraries and private collections and searching through printed sources, and cataloguing instruments. Its a massive task, probably several years work by a team of people. The sources are spread around the world, Europe, N America, S America, S Africa and possibly more.
I'll say again, its a great idea, but whoever takes it on has to go in with their eyes open and realise what an enormous task it is.
-
How about we take a turn at looking it from the other end and see how far we can get with a complete history of the Hohner Pokerwork? Shy Talk has already provided a skeleton in the FAQ thread, how about we see how far the 'hive mind' of this forum can get at puttiing together a definitive history of the instrument by way of forum posts? If we succeed we'll have a better idea of how the database should work. If we can't then we'll at least have saved the effort of building a database that's unlikely to be filled.
-
Good idea, and it also points up something that would not fit easily into a flat file database, that is the history of changes and developments in a single model.
-
Hi Theo
I understand where you are coming from in considering the amount of work needed to plan and implement as complete a database as is possible. I agree that a such a resource would be a monumental task but the 'hive mind' version, as Waltham puts it, is the organic route I was proposing.
I only ever envisaged an organic information source which would be updated on an as and when basis by the members. This was promoted by reading threads in the Instrument Makes and Models section and thinking wouldn't it be a good idea if this information were recorded in an orderly, searchable repository instead of being piece meal in different threads. I also thought it should be an integral part of Instrument Makes and Models but have no idea how that can be achieved.
I could see a flat database working for this with the history of changes being catered for in the the first few fields of Make, Model and Mark. Each unique mark would be recorded as a separate record or as a sub section of the home record. A search on listings would bring up these three items, together with other key elements, which would allow the researcher to choose. A simple MS Works Database does the whole job except pictures. A database with combo boxes would also be beneficial in speeding up both entries and searches.
The wonderful fact sheets from Hohner refereed to by Bill can be entered on an as and when basis by anyone who was interested in a particular mark. Each member could enter the details of their own 'exotica', - see Sebastian's friend Anders Trabjerg and his mid-1930s, 8-voice, 1.3-row D/C# Baldoni, Bartoli for real exotica and I'm sure there is more.
Once a vehicle is in place, makers could be advised to check entries about their products and to update us with new offerings. The work could and should be spread and the project should evolve over time. You are quite right Theo, it is too much work for even a small team but open to the community it could happen.
-
Hi Theo
I understand where you are coming from in considering the amount of work needed to plan and implement as complete a database as is possible. I agree that a such a resource would be a monumental task but the 'hive mind' version, as Waltham puts it, is the organic route I was proposing.
Ah I see, so the idea has changed then, I was still thinking of your original proposal for:
What about a History section with full details of every maker and model ?
I could see a flat database working for this with the history of changes being catered for in the the first few fields of Make, Model and Mark. Each unique mark would be recorded as a separate record or as a sub section of the home record.
But what you are proposing there is squashing the data into a flat file, when the structure of the data is actually more complex and really would justify a relational database approach, especially as the volume of data grows.
simple MS Works Database does the whole job except pictures. A database with combo boxes would also be beneficial in speeding up both entries and searches.
But for the cooperative approach you are proposing, and working on the web you would be unable to use MS Works. You would need to used a multi-user, web capable database, and the one which I see used for the majority of web based databases is MySQL. This forum runs on a MySQL database, and the information part runs on another. If you want to start with a bare MySQL database you would end up doing a lot of scripting to create a front end with access rights, searches, and various outputs. It might appeal to any PHP writers on the forum, but its also not a trivial job. That is really why I suggested using a Wiki, or there may be other public domain/open source scripts we could use.
I also thought it should be an integral part of Instrument Makes and Models but have no idea how that can be achieved.
would not be a problem if the thing is built along the lines described above.
-
As you can tell from my ramblings I am no programmer Theo and I agree that a relational database would be ideal. I also know the cost of commissioning such wonderful items. The only reason I suggest MS Works 'type' databasing is that even I can programme that. I have heard of MySQL and know it is the thing for the net but there my knowledge ends. I am in the hands of others to guide me in the right direction to create the needed tool. To answer one of your earlier questions, yes I am only too willing to help within my knowledge and abilities.
Sorry I was unclear in the first instance. I see now that the original bar was much too high but it was a concept to aspire to and at that time I had no idea as to the volume of makes, models and marks which are obviously out there.
To echo your remarks, using a Wiki, or there may be other public domain/open source scripts we could use.
does anyone know of a tool which will do the job without extensive work in making it fit ?
-
I don't where the database is to be located but images are not disk-storage friendly and come in 57 varieties - tif,bmf,jpg etc
You have to store only references to the picture-files, e. g. "http://your.server.here/pictureOne.jpg; http://your.second.server/secondPicture.png". The picture-files could be located on different servers, this shouldn't be a big problem.
History of changes: This could be dealt with in the remarks-field. Maybe "remarks" isn't a really good english translation. But I would want to put everything not easily classified into this "remarks-field", that could be several paragraphs of text, if appropriated.
-
Y'all have seen this, no doubt, but I don't think it has been mentioned so far in this thread.
http://www.accordion-wiki.com/index.php?title=Main_Page
Tom
-
Hello All,
I've been lurking on this site for a few weeks now and have found it to be most interesting, having been a somewhat soliatary melodeon player (if I even qualify as that) for a number of years now. Having never really met or played with any other box players, it's been quite a revelation to discover what goes on.
Anyhow, upon reading this thread, I decided it was time to break my silence, as I think I know what you need. If you're wanting a community based wiki system, but with the structure and reporting of a regular database, then you should be looking at something called Semantic MediaWiki (http://semantic-mediawiki.org/wiki/Semantic_MediaWiki (http://semantic-mediawiki.org/wiki/Semantic_MediaWiki)). It's an extension to (i.e. it sits on top of) MediaWiki that allows users to 'mark-up' pages with information of a specific property. So, for instance, on an melodeon page, information such as maker, number of rows, key, voices, weight could all be recorded specifically and subsequently queried (a regular wiki can't do this). What's more, using the additional Semantic Forms extension, an interface can be created that guides users through the page creation process, meaning that average users don't have to know how the system works or what they're supposed to be creating - they just fill in the boxes.
I've been using and administering such a system, in our office, for 6 months now and, on the whole, it's worked very well. When setting it up initially, it does take more time and knowledge that a regular wiki would. However, the eventual results are worth the effort. Bearing in mind what's been requested above, I think it would be worth consideration.
To set up and host such a system locally, you'd need a web server, MySQL, PHP support and a regular Mediawiki install, along with the Semantic extensions (all this is freely available for no charge). Alternatively, there's a site that publicly hosts this sort of wiki. It's at http://www.referata.com/wiki/Main_Page (http://www.referata.com/wiki/Main_Page) (I've no experience of using this service, though).
Anyhow, hope this is of some use.
Guy
-
To set up and host such a system locally, you'd need a web server, MySQL, PHP support and a regular Mediawiki install, along with the Semantic extensions (all this is freely available for no charge). Alternatively, there's a site that publicly hosts this sort of wiki. It's at http://www.referata.com/wiki/Main_Page (http://www.referata.com/wiki/Main_Page) (I've no experience of using this service, though).
Anyhow, hope this is of some use.
Guy
Thanks for the suggestions Guy. All the server facilities you list are available on our server.
-
Working at the moment, just dropped in to see how things are going on only to find we've struck gold. Thanks Tom & Guy. I've had a quick look and will look properly this evening but first impression is that this is what we need. Theo says it will work on melodeon net - great.
Back later
-
we've struck gold.
It looks very fine indeed.
Amicalmen,
Sebastian
-
Working at the moment, just dropped in to see how things are going on only to find we've struck gold. Thanks Tom & Guy. I've had a quick look and will look properly this evening but first impression is that this is what we need. Theo says it will work on melodeon net - great.
Back later
Mind you there is a bit of work setting up the structure. I'm happy to install a copy of Semantic MediaWiki on out server, but I don't wish to do the development work that will be needed. Volunteers???
-
Working at the moment, just dropped in to see how things are going on only to find we've struck gold. Thanks Tom & Guy. I've had a quick look and will look properly this evening but first impression is that this is what we need. Theo says it will work on melodeon net - great.
Back later
Mind you there is a bit of work setting up the structure. I'm happy to install a copy of Semantic MediaWiki on out server, but I don't wish to do the development work that will be needed. Volunteers???
Well, as I already have experience in setting up and running such a system, I guess it would be a bit lame if I didn't offer at least some sort of help. I would recommend, thought, that there should be at least a couple of other that are prepared to get their hands dirty and learn how it all works.
In the first instance, though, the following would need to be done:
- On the server, you'd need to install the Semantic Mediawiki, Semantic Forms, Semantic Drilldown (preferably) and, if it's not already installed, the Parser Function extensions. If Mediawiki is already in place, these are all easy to find and install - they're all on the official extensions matrix. There are a few others that could be installed too, but I think you're better off starting simply.
- On your base Mediawiki install, ensure image support is turned on (I think it's off by default). Photos and diagrams are cool!
- People need to start thinking seriously about what types of standard page are needed, so appropriate properties, templates and forms can be created. To start with you need to think of wiki pages in terms of simple categories. These might be 'Instruments', 'Manufacturers', 'Players', 'Repairers', 'Events' etc - it depends what content you'd want to cover. To begin with, you'd want a list, however small, that makes a cohesive working system. Once you've got these categories defined, you'll need to figure out what common properties you'd need in each (and also, eventually, what type of data they'd hold). So, for an 'Instruments' category, you might have name, number of voices, number of rows, key, date first sold, manufacturer, web link, summary, notes - really, any fields you think might be necessary, even if they're not a relevant for every entry. Once a few of the categories are sorted out and agreed upon, it's then fairly straightforward (once you know what you're doing) to build them into the system. Other pages, that report and use the data, follow on naturally after that (no need to worry about that right now).
Guy
-
Earlier in the post I submitted a proposed field list which I have been updating at home as people add ideas and wish items. Once I have tidied it up in the next day or two I will post it. I am willing to be one of the helpers, data, structure, analysis etc but I have no programming skills.
Once the tool is in place I would be willing to write to every manufacturer (that I know of or I am given the email address of) advising them of the facility and asking them to submit details of their products (by filling in the entry form themselves) and to check the details we already have from 'the hive'.
The other massive source of info is within this forum under the new remit of Lester's FAQ section. Shy Talker and Waltham have also supplied solid information, indeed Watham has already begun with the history of the Polka Work. We should also request the assistance of our overseas members to enlighten us with offerings from other countries.
-
Earlier in the post I submitted a proposed field list which I have been updating at home as people add ideas and wish items. Once I have tidied it up in the next day or two I will post it. I am willing to be one of the helpers, data, structure, analysis etc but I have no programming skills.
Unless you're thinking of doing something well out of the ordinary (unlikely, given what's been posted so far), no conventional programming is required. Data, structure and analysis skills are very useful, though, as is the ability to think up unambiguous terms for the properties and categories.
Another useful skill, albeit one that isn't necessarily required right away, is a bit of graphics and design finesse.
Guy
-
Hi.
Sorry for ducking away for some days, but we had a little bit more to do at work due to the Asse-problems (http://www.dw-world.de/dw/article/0,,3618649,00.html) becoming more urgent. >:(
If there is some help, I could provide, in setting up the system, I would be glad to do so. For programming skills: I scripted together with other volunteers a member administration system for an organisation with 4000+ members or a web shop for books for a friend, I fiddled with some AJAX-applications and set up a simple Wiki for some small organisation. So I have a basic knowledge of PHP and MySQL. However, until now I know nothing about the internals of the Wikimedia-system.
Sebastian
-
Hi!
I have been writing my accordion web pages since 2006 (release Jan. 1st!). It includes mostly history and technical issues of accordions. In my site there is accordion gallery with over 700 pictures (and going up) and this gallery is only one part of the site. Today I can say that my web page is more complete than any wikipedia today (in mount of information, not languages). Acc.gallery is not such database you have been thinking here but for me it have been very good tool to understand the historical issues more correct. My gallery includes picture + name + tuning (if a diatonic) + manufacture and place + other important issues like history of that accordion shown in the picture.
As my job has gone further, I have understood that it will never stop. Never. Only in Italy there have been 419 manufactures between years 1850 - 2003. Then there is Russian industry, European, Asian, American... concertinas, bandoneons, diatonics, chromatics... My field includes every single free-reeded European origin instrument and some very early mouth organs (i.e. everything about free-reed instruments). My project is once in a lifetime project and a lifetime project...
My site is released here www.vapaalehdykka.net in Finnish. Later on I am going to take more domains. Then there is translation coming for English, Swedish and perhaps German too.
-
accordion web pages since 2006 (release Jan. 1st!). It includes mostly history and technical issues of accordions. In my site there is accordion gallery with over 700 pictures (and going up) and this gallery is only one part of the site.
That sounds interesting. Since I didn't find any accordion on the given address, I suppose you mean release date 2009-01-01?
Sebastian
-
Being a retired technogeek and professional anorak, I thought I would see how easy it was to set something up like what has been suggested on my Linux system. Using the fields suggested so far you end up with something like this:
-
Being a retired technogeek and professional anorak, I thought I would see how easy it was to set something up like what has been suggested on my Linux system. Using the fields suggested so far you end up with something like this:
Brilliant! :D
(Although I don't like Ubuntu. ;D )
If two models have the same name, you would set up disambiguation pages, right?
How do you create lists, lets say I'm looking for two-row instruments with two treble reeds per tone? There should be some footer on the pages, if I understood the desription of the semantic wiki correctly.
I can, of course, search for instruments with a specific first-made-year. But is it possible to list the models chronologically or e. g. according to weight?
How does the wiki-code for this page look?
Thanks for the nice example. :-*
Sebastian
-
Sebastian
I've never used a wiki before except to look thing up, so I know nuffin, guv. I just loaded it all up on Ubuntu because I didn't want it on my Windoze system. The code for that page looks like this:
{{Model|Hohner|2915|Pokerwork|1955|-|21|2|-|8|3|-|T|Swing|Wood|16 cm|30 cm|29 cm|2.5 kg}}
Black and gold finish
[[Image:2915.jpg|thumb|none|2915]]
The template for it, etc is more complicated though. To do the sort of things you were talking about I assume you would set up queries. That's where you need experience.
-
accordion web pages since 2006 (release Jan. 1st!). It includes mostly history and technical issues of accordions. In my site there is accordion gallery with over 700 pictures (and going up) and this gallery is only one part of the site.
That sounds interesting. Since I didn't find any accordion on the given address, I suppose you mean release date 2009-01-01?
Sebastian
Yes. 1.1.2009 :-)
-
Then there is translation coming for English, Swedish and perhaps German too.
You may find people here who would help with the translation, I don't know for sure, but it could be worth asking.
-
Being a retired technogeek and professional anorak, I thought I would see how easy it was to set something up like what has been suggested on my Linux system. Using the fields suggested so far you end up with something like this:
Woah, I think that was a very cool thing to do. I suspect that just the image of that page will be reason enough to get people really thinking about what they want and what might be possible.
In an attempt to further stimulate progress, here's my thoughts on what you've shown and some of the points that followed it.
- Firstly, from the lack of a 'factbox' at the foot of the screen*, I'm assuming that your page was created using standard Mediawiki, not Semantic Mediawiki (SMW). If you're new to wikis, then this is a sensible way to start - pretty much everything you learn with the basic system will apply with the Semantic version too.
- By not using SMW at this stage, you're doing a good job in demonstrating why it would be worth having. For instance, if I wanted a list of all melodeons that have swing tuning and two rows, the only way to do it with a standard wiki system would be to look through all of the pages manually, perhaps using Search to help you along. Even though the information is there on the page for all to see (apparently organised in a systematic way), the wiki has no way of knowing what it means and can't therefore query on it. This gets straight to what SMW is for - adding meaning to information, so that you can then get proper access to it.
- Another advantage of SMW (or, specifically, Semantic Forms), is made obvious in your page source - specifically this bit (the template call...):
{{Model|Hohner|2915|Pokerwork|1955|-|21|2|-|8|3|-|T|Swing|Wood|16 cm|30 cm|29 cm|2.5 kg}}
Although calling templates like this is in many ways simple, it's absolutely not user friendly and is susceptible to error. Although SMW still uses this format under-the-covers, it also allows you to create a 'form' which will guide any user through the page creation, requiring no previous knowledge of the system at all. You just fill in the boxes that are given. Once it's set up, this is a much more friendly way of doing it.
(Incidently, I see that you used the 'ordered' approach to the parameter calls. Although this works, it's generally much better to used named parameters - it'll save a lot of strife in the longer term.)
- As can be seen from the image, there are likely to be a few different data types required. Even on that page, there's text, numbers, dates, measurements and weights. When setting up a SMW page, you get to choose the type of each field. Thus, when you get to the reporting stage, the system is able to properly understand what you mean if you were to ask for First Made dates between 1950 and 1960.
- On the subject of datatypes, I see that 'Hohner' is actually a link to another page (just as you'd expect). This makes this a property of page type 'Page' - thus, although it acts as a link, it can still have meaning and be queried, just like any other field. If, for example, the Hohner page itself didn't actually exist yet, it would be possible to associate the link type with a form, meaning that someone clicking the link would actually be taken to the Manufacturer form, rather than just an empty page.
- One of the tricky things in any Wiki (and particularly in SMW) is making sure that you use the most appropriate name for pages, categories, properties (SMW only) and that you don't end up with lots of duplicate or ambiguous entries. There's no absolute magic way of solving this, but SMW can at least help in a number of ways. Firstly, by making sure that all of the key pages have associated template and forms, you can strongly encourage people to enter the data that you're hoping for. Also, with Semantic Forms, it's now possible to generate a page name from one or more of the fields, thus, in theory, ensuring that page naming is consistent and meaningful. So, on the page shown, it would be possible for the page name to be automatically set as 'Hohner Pokerwork 2915', even though the information would be taken from separate fields. As page names are so important in Mediawiki, this feature can be a big bonus, should you choose to use it. If there really were two page entries with the same name, the system could automatically add a '_2' (or whatever number was next in the sequence), ensuring that they were different. (disambiguation pages are a different matter - I'm not experienced with doing these in SMW, but I think it's no different from creating the in Wikipeadia).
- One thing that your entry is missing is a short summary. Although it might not mean too much on the page itself, it's very handy to have a small description when you're generating reports and listing lot of entries at once. Other fields that you might not immediately think about might include 'Entry Date' (date wiki page was created, which can be populated automatically) and possibly a 'Comments' box, although this might be better served with just free text that sits under the template.
- Another suggestion that works well with SMW is to include one or more 'new' pages in the Navigation box on the left of the screen. That way, if someone just wants to input details of a new instrument, they just click, say, New Instrument in the box and that will immediately open up the relevant form. No need to navigate to any pages beforehand!
- Lastly (I apologies that this is a lot of reading...), it's worth thinking about what might be on a Manufacturer page. It might well include manufacture name, address, e-mail, website etc, but it could also include a report that lists all of their models, queried automatically from the instrument pages themselves and effectively self-updating. Cool, eh?
Hope this is of some use. Again, if you need any assistance in getting the SMW thing up and running, please let me know.
Guy
* in SMW, it's possible to turn the factbox off, making it hard to tell, 100%, whether you're using SMW or not. Apologies if this is the case.
-
Guy
You've got the job,
Theo
-
Been a bit busy this week but here's the proposed field list (let me know if I've missed anyone's best ideas.
Field Type of Field Details
Record ID Numeric
Manufacturer General Link to manufacturers database
Model Name General
Model Mark General
Tradition built for General
First Made Date
Last Made Date
Associated marks General Other brandings
No of Treble Buttons Numeric
No of rows General
No of treble reeds Numeric
No of treble registers Numeric
No of bass Buttons Numeric
No of bass reeds Numeric
No of bass registers Numeric
Type of reeds General Tipo mano etc
Keys available General GCF, ADG etc.
Original Tuning General Swing, Tremolo etc
Case General Wood. pearloid, decoration etc
Height Numeric auto conversion between metric & imperial
Width Numeric ditto
Depth Numeric ditto
Weight Numeric ditto
Comments General General note field
Picture Field Gallery
Taking on board others comments, the manufacturers field should be a linked database which when clicked gives address and contact details if they are still in business or their last trading premises if they are defunct. It may also be able to show when companies have moved premises.
I think the response so far has been fantastic and I confirm that I will do whatever I can to help. I do feel a project leader would hold it all together but before anyone asks, I don't think I have the relevant experience. Count me in as an active team member.
-
If you accept Guy, I'll volunteer for the team.
-
On the understanding that Theo already has/will have the server-side requirements in hand, then yes, I'd be happy to do (or lead) the initial development and get the thing up and running.
Guy
-
Been a bit busy this week but here's the proposed field list (let me know if I've missed anyone's best ideas.
I'm cheering this on from the sidelines . . . how about an optional lookup link to keyboard diagrams. That seems to be a commonly occurring question about unfamiliar instruments, and many of the diagrams already exist.
-
- By not using SMW at this stage, you're doing a good job in demonstrating why it would be worth having. For instance, if I wanted a list of all melodeons that have swing tuning and two rows, the only way to do it with a standard wiki system would be to look through all of the pages manually, perhaps using Search to help you along. Even though the information is there on the page for all to see (apparently organised in a systematic way), the wiki has no way of knowing what it means and can't therefore query on it. This gets straight to what SMW is for - adding meaning to information, so that you can then get proper access to it.
I did use SMW, properties, templates, forms, etc to produce all this, the factbox is off the bottom of the page. Fuller reply to follow, I'm in Germany on my daughter's German keyboard with all the letters in the wrong places. There is a Manufacturer template, etc as well, but not much on it.
-
I did use SMW, properties, templates, forms, etc to produce all this, the factbox is off the bottom of the page. Fuller reply to follow, I'm in Germany on my daughter's German keyboard with all the letters in the wrong places. There is a Manufacturer template, etc as well, but not much on it.
Ah, that's excellent, then. As I mentioned in the previous post, it was impossible to tell, from the image alone, one way or another. I look forward to hearing more.
-
how about an optional lookup link to keyboard diagrams.[/quote]
Keyboard diagrams would probably be the best way of showing items in the 'Keys Available' field.
Guy you asked about graphics earlier - fortunately this is my field and I can provide almost anything you want in any format you want. Keyboard maps for instance are a doddle.
I do favour Casatgnari's convention of showing push on the top row and pull on the bottom row. eg. below
As Mathew says most layouts are freely available anyway and can be manipulated to a standard presentation.
-
how about an optional lookup link to keyboard diagrams.
Keyboard diagrams would probably be the best way of showing items in the 'Keys Available' field.
Guy you asked about graphics earlier - fortunately this is my field and I can provide almost anything you want in any format you want. Keyboard maps for instance are a doddle.
I do favour Casatgnari's convention of showing push on the top row and pull on the bottom row. eg. below
As Mathew says most layouts are freely available anyway and can be manipulated to a standard presentation.
[/quote]
Yep, sounds good. It'll be no problem to create individual pages showing images of keyboard layouts. If they are all done in a consistent manner, then so much the better. From what I've seen elsewhere on this site, the actual naming of layouts seems somewhat awkward. As names are a fundamental part of a wiki, it would probably be a good idea to formulate a standard approach to this right from the start (i.e. is it good or bad that a keyboard layout is given a manufacturers/players name?). I really have no idea what form this might take - that's one for the actual melodeon experts among you.
Other design/graphics that might be required could include:
- A main 'welcome' image to fill the Home screen. My general view is that the home screen should contain little information (just a few links, at most) and be locked from general update, to ensure that there's always a decent and consistent looking entry point to the system.
- A logo for the top corner. Bill's instrument picture works well, but I'm guessing that something created specifically for the job could give an even better sense of site ID. Also, it's worth creating this with an alpha transparency channel, so that the background shows through properly and doesn't leave a rectangular block around the edge (unless that's what you want in the design).
- A 'wallpaper' background, to replace the one in the default skin. Needs to be subtle and preferably to fade out from top to bottom, as the original does. Maybe an abstract image based on buttons or grill design?
- A consistent look (fonts/borders/colours/line styles) to be used accross all templates. Pages, templates and forms tend to default to a relatively simple look, but there's every opportunity to individualise these. Most things that can be done with HTML and CSS work in the wiki too. Because of the template system, looks can be evolved or changed over time, without having to worry too much about the actual page content. So, lots of potential here, if someone wants to play.
- Plus, of course, any diagram or images that are specific to the content itself. Keyboard layouts you've mentioned, but are there other diagrams that might be required?
Guy
-
I'm cheering this on from the sidelines . . .
Me too! Unfortunately I have neither knowledge or skills to contribute here, so I'll just be a grateful recipient of all the hard work - for which many thanks in advance.
Pete.
-
I'm cheering this on from the sidelines . . .
Me too! Unfortunately I have neither knowledge or skills to contribute here, so I'll just be a grateful recipient of all the hard work - for which many thanks in advance.
Pete.
If this works out well anyone will be able to contribute details of instruments that are not already listed.
-
OK, time to suggest a way forward.
1. Firstly, now that he's worked his way through the SMW process, I'm interest to hear Bill's comment on SMW and the its suitability to this project. Also, any concerns, confusions or overall impressions he might have had. It's some while since I went throught that same process, so a fresh perspective could be very valuable.
Then, assuming that Bill doesn't come up with a show stopper....
2. If the system is to be hosted on Theo's server, we need confirmation that SMW is installed, running and available. As mentioned before, I would suggest starting with the Semantic Mediawiki, Semantic Forms, Semantic Drilldown and Parser Functions extensions installed. Also, if Mediawiki is already installed, which version is it? 1.13?
3. Obviously, for any of us to get started on the system, we need the URL of the wiki's home page. Initially, I'd suggest making the URL known to developers/volunteers only, otherwise things could get a bit chaotic. Also, at least one of us will need access to the WikiSysop account, so that the navigation bars can be amended.
4. Another job to be done soon will be for Theo (or whoever the system admin is) to establish a Mediawiki security policy. Although I'd expect that everyone will be able to view the wiki, you might want to think about if/how edit access is controlled. At the very least, I'd suggest that annonymous users are barred from editing (i.e. if you want to edit, you need to sign up with a user account). That way, if someone does contribute rubbish or spam, at least they can be dealt with and held responsible.
5. Can I suggest that an additional forum section is set up for this project? I suspect that communicating via this one thread could get confusing.
6. I'm suspecting that the eventual success/failure of this project will depend on how well the instrument database is specified. Although the structure can be altered once its up and running, this can prove troublesome if lots of records need changing. It's much better to get it right to begin with.
The field lists suggested already look to be a good start, but there's still some factors to be considered further. Aside from giving a field a datatype, it's also possible to specify a list of values that might be contained in it. So, for example, when filling in the 'Keys Available' field, it would be possible to force the user to choose from a drop-down list of options (DG, CF, BC...), rather than expect them to enter text themselves. This can be very useful, as it ensures that people will use a common terminology and thus makes querying much more effective. The downside is that the list forces the person to choose one of the options - they can't enter something that isn't there without first editing the list. Editing the list is done elsewhere in the wiki - it's not hard to do, but isn't at all obvious to a casual user, which may or may not be a good thing.
So, against the lists already suggested, which fields would require a specific list of values and what would those values be (initially, at least)?
Also, does anyone have any issues with the exact wording of the fields that have already been suggested. Are any ambiguous, confusing, or only specific to a sub-set of instruments? I know from experience that its very easy to get the naming side very wrong, so it's definately worth some proper thought. So, do the name and statistics from your own instrument(s) fit the suggestions made so far?
Finally, what sort of instruments will be included in the wiki and which won't? Given the name of this forum, I'm guessing that concertinas and piano accordions won't be included, but what about the some of the more regional melodeon variations? Where would you state that an instrument is an organetti or trikitixa? Or, doesn't that matter?
Guy
-
The Hohner section alone would be ginormous! (Considering all the different models they've built in their own right since they started making accordions in 1903, and all their sub-brands, and ones made specially for distributors.) It's mind-boggling... :o
To give some idea of what I'm talking about, I've a very complete catalogue of the Hohner (plus sub-brands) range circa 1929-30, and it lists no less than 250 standard models (+ variations!) of what we'd today (at least in England) describe as "melodeons" for that year alone, though not including lots of "own-line" specials for distributors... :o
-
OK, time to suggest a way forward.
1. Firstly, now that he's worked his way through the SMW process, I'm interest to hear Bill's comment on SMW and the its suitability to this project. Also, any concerns, confusions or overall impressions he might have had. It's some while since I went throught that same process, so a fresh perspective could be very valuable.
Then, assuming that Bill doesn't come up with a show stopper....
2. If the system is to be hosted on Theo's server, we need confirmation that SMW is installed, running and available. As mentioned before, I would suggest starting with the Semantic Mediawiki, Semantic Forms, Semantic Drilldown and Parser Functions extensions installed. Also, if Mediawiki is already installed, which version is it? 1.13?
Nothing installed yet, just d/ld Mediawiki 1.13 Will try and get them installed this week.
3. Obviously, for any of us to get started on the system, we need the URL of the wiki's home page. Initially, I'd suggest making the URL known to developers/volunteers only, otherwise things could get a bit chaotic. Also, at least one of us will need access to the WikiSysop account, so that the navigation bars can be amended.
Agreed
4. Another job to be done soon will be for Theo (or whoever the system admin is) to establish a Mediawiki security policy. Although I'd expect that everyone will be able to view the wiki, you might want to think about if/how edit access is controlled. At the very least, I'd suggest that annonymous users are barred from editing (i.e. if you want to edit, you need to sign up with a user account). That way, if someone does contribute rubbish or spam, at least they can be dealt with and held responsible.
Yes, something for the project group to work out the details of
5. Can I suggest that an additional forum section is set up for this project? I suspect that communicating via this one thread could get confusing.
Will do
6. I'm suspecting that the eventual success/failure of this project will depend on how well the instrument database is specified. Although the structure can be altered once its up and running, this can prove troublesome if lots of records need changing. It's much better to get it right to begin with.
Yes, for example:
1 , "number of bass reeds" There are so many different ways to count this. Its easy for a stradella bass, just count the number of reed banks, but in diatonics there are usually different numbers for bass and chord, and sometimes reeds are shared between bass and chord. So if this is included we would need no of bass reeds, no of chord reeds, number of shared reeds, and their are exceptions to this too where some reeds are shared between different chords.
The field lists suggested already look to be a good start, but there's still some factors to be considered further. Aside from giving a field a datatype, it's also possible to specify a list of values that might be contained in it. So, for example, when filling in the 'Keys Available' field, it would be possible to force the user to choose from a drop-down list of options (DG, CF, BC...), rather than expect them to enter text themselves. This can be very useful, as it ensures that people will use a common terminology and thus makes querying much more effective. The downside is that the list forces the person to choose one of the options - they can't enter something that isn't there without first editing the list. Editing the list is done elsewhere in the wiki - it's not hard to do, but isn't at all obvious to a casual user, which may or may not be a good thing.
Something else for the project group to hammer out
Another suggestion: its common for one model to be produced in several tunings, and in several different finishes and colours so for one model there needs to be the ability to assign more than one attribute from a list.
So, against the lists already suggested, which fields would require a specific list of values and what would those values be (initially, at least)?
Also, does anyone have any issues with the exact wording of the fields that have already been suggested. Are any ambiguous, confusing, or only specific to a sub-set of instruments? I know from experience that its very easy to get the naming side very wrong, so it's definately worth some proper thought. So, do the name and statistics from your own instrument(s) fit the suggestions made so far?
Finally, what sort of instruments will be included in the wiki and which won't? Given the name of this forum, I'm guessing that concertinas and piano accordions won't be included, but what about the some of the more regional melodeon variations? Where would you state that an instrument is an organetti or trikitixa? Or, doesn't that matter?
Including regional names sound useful
Guy
-
5. Can I suggest that an additional forum section is set up for this project? I suspect that communicating via this one thread could get confusing.
Done.
It's in the Forum and Website Admin area.
At present its accessible to all members, but not guests. It could be made a closed group if necessary.
Should this thread be moved there?
-
5. Can I suggest that an additional forum section is set up for this project? I suspect that communicating via this one thread could get confusing.
Done.
It's in the Forum and Website Admin area.
At present its accessible to all members, but not guests. It could be made a closed group if necessary.
Should this thread be moved there?
Thanks, Theo. Not sure whether this thread should be moved right now. Might be worth leaving it here for the time being (maybe locked), until everyone's worked out what's going on.
Also, your comment about some fields needing several entries was correct - I really should have mentioned that before. The SMW has a couple of ways of handling such data, so it shouldn't be a problem.
Guy
-
Yep, sounds good. ... From what I've seen elsewhere on this site, the actual naming of layouts seems somewhat awkward. As names are a fundamental part of a wiki, it would probably be a good idea to formulate a standard approach to this right from the start (i.e. is it good or bad that a keyboard layout is given a manufacturers/players name?). I really have no idea what form this might take - that's one for the actual melodeon experts among you.
A good place to start would be the manufacturers "Standard" which would have several key choices plus low notes or accidentals. I note where keyboard maps are named on this site it has been done under the name of people who are well known in folk circles. The nature of the beast is of course that most manufacturers offer bespoke layouts. The current nomenclature of 1, 1.5 row etc could be modified to stating the number of buttons per row which would give a unique number eg. 9+3 (Organetto) 11+10 (Hohner & most other two rows) 9+10+9 (Rucksack steirische) etc. Possibly, at the risk of getting too complex, add the bass buttons. eg. 11+10+5/12 (Castagnari Dony & others) Individual layout variations could be shown further down a page covering that particular number of buttons. If we create pages of layouts can these be accessed by hyperlinks from the Make & Model page ?
Theo's 'inside' knowledge of construction has highlighted how to describe bass reeds as opposed to buttons. Probably this detail can be in the body text but for identification purposes most people will want to know the maximum number of reeds that will sound when a button is pushed.
-
I did use SMW, properties, templates, forms, etc to produce all this, the factbox is off the bottom of the page. Fuller reply to follow, I'm in Germany on my daughter's German keyboard with all the letters in the wrong places. There is a Manufacturer template, etc as well, but not much on it.
Ah, that's excellent, then. As I mentioned in the previous post, it was impossible to tell, from the image alone, one way or another. I look forward to hearing more.
I have put my response to previous posts here (http://forum.melodeon.net/index.php?topic=852.msg7074#msg7074), as Theo has created it. I can't volunteer to be a melodeon history expert, as I don't have a collection of old catalogues to peruse, and I can't be an expert on SMW, because I just followed my nose, but I can volunteer to try things out, as I have an almost virgin throw-away installation.