The goal of a database is to store data, organized data. It is not to produce books. If the data is available, you can do what you want with it, including producing books. We should not mix data, and action on data. The current design of test.selapa.net is very fine. I see nearly nothing to add. But I do not agree on the change made on http://test.selapa.net/gregobase/chant.php?id=3043 [3] the 22 may as it is done now. The gabc database sould keep the 2 versions of Tantum Ergo III : original as in _Chants of the Church, Solesmes, 1956_, p. 145, with the 'j' of 'jubilatio', and another version, with some more tag, let us call it the "i" tag, with the 'i' of 'iubilation'. This is what should be in the database. Now, what should be displayed in http://test.selapa.net/gregobase/chant.php?id=3043 [3] ? There are many solutions : - display as it is now (but the database remains rich of the 2 versions, the data is here for the future) - add some link in http://test.selapa.net/gregobase/incipit.php?letter=T [4] so that the user chooses the original version or the "i"-tagged version such as : Tantum ergo. III (Solesmes) ("i" tag) - add some cookie to allow the user to store preferences... - etc The point is to keep the DB rich of all the options, and not to decide what is "good" gregorian... (even if personally I prefer the "j" allowing to differentiate "i" voyelle de "j" consonne) (I like GregoBase name, I propose gregobase.selapa.net )
Le 22/05/2013 19:45, pierre a écrit : > Mmm, I am sorry to disagree with many of us. > The gabc database should not be a standard of what is "good" gregorian score. > It is not to "us" to decide if we must use i or j, or mass of PAul VI or > older one. We should remain open. "We" are a tool. Only. > It seems to me that the only possible way is to have a gabc database as near > as possible of each original book. > If there are many different versions of one hymn in different books, we must > have the correspondant entries possible in the DB. > The fact that the entry is filled is another question. It will be filled if > someone fills it. But the DB should remain open. > This could lead to a standard "de facto", if some entries are filled and > other ones are not... > But that should not be "by design". > The reference to the original book seems enough to recognize various > variants. > And I see no problem if gabc data is more or less duplicated... > > Le 22/05/2013 16:58, Olivier Berten a écrit : > >> Well... I'm actually wondering myself... because I like to be as close >> as possible as the source but it doesn't really make sense to me to >> have different entries for the Graduale and the Liber versions. One >> could argue that we should use some standardised latin (same with the >> oe/ae/œ/æ or i/j question). >> >> But on the other hand the Liber gives a lot of information for people >> less litterate in that topic which could be useful aswell: accents for >> the people less used to the tonic accent placement in latin or noted >> psalms for people less used to psalmody... >> >> I also wonder how to deal with the hymns with one different verse for >> different occasions, or which are a port of another hymn... >> >> I'd love to have other peoples opinions >> >> 2013/5/22 Jacques Peron <[email protected]>: >> Hello, >> >> I'd have a question about the rules to be followed on your database. >> >> There are differences between editions of gregorian chants : >> - the Graduale puts accents on words only when they have 3 or more syllabes, >> while the Liber usualis and others put accents on all accented words ; >> - liturgical books use i in place of j after 1962, but not before ; >> - æ is often written ae, I think because they had no easy mean to do >> otherwise (but I can't be affirmative). >> >> So here is my question : is it better to follow the presentation of the >> source in every case (but some chants can be different between different >> sources), or to follow uniform rules ? In such a case, would it be possible >> to give those rules, for example on the Participate page ? >> >> Please forgive me if I made English mistakes, >> >> Fr. Jacques Peron. >> >> 2013/3/24 Olivier Berten <[email protected]> >> Hi! >> >> Little by little, I'm getting further in my gregorian database system. >> There is now an editing interface. It's not very user-friendly yet but >> my knowledge in gui conception and programming is very weak... So if >> you want to help, I'm very open to it! >> >> You can also just proofread the scores and check the little "Me" >> button under "Proofread by" (if you don't see any mistakes, of >> course). >> >> For those interested, I published the source code on GitHub >> <https://github.com/olivierberten/GregoBase> [1]. It's a mess... but if >> you're very brave, you can have a look at it ;-) >> >> Olivier >> >> _______________________________________________ >> Gregorio-users mailing list >> [email protected] >> https://mail.gna.org/listinfo/gregorio-users [2] >> >> _______________________________________________ >> Gregorio-users mailing list >> [email protected] >> https://mail.gna.org/listinfo/gregorio-users [2] > > _______________________________________________ > Gregorio-users mailing list > [email protected] > https://mail.gna.org/listinfo/gregorio-users [2] Links: ------ [1] https://github.com/olivierberten/GregoBase [2] https://mail.gna.org/listinfo/gregorio-users [3] http://test.selapa.net/gregobase/chant.php?id=3043 [4] http://test.selapa.net/gregobase/incipit.php?letter=T
_______________________________________________ Gregorio-users mailing list [email protected] https://mail.gna.org/listinfo/gregorio-users
