Adding / changing tag should not activate card changed-switch
I've got 4 "child"-databases and one master-db. All cards (vocabulary, seperated by tags for the learning-years) are only changed in the master-db, then exported and imported in the child's database. Each child-database is synchronised with the child's mobile, so everyone has his individual set of cards and learning-infos.
Everything o.k., but ...
if I have to change a tag (e.g. adding one child's learning level, so that he/she gets this word, too), the whole card seems to be marked as changed and causes duplicate cards in the children-databases [because of the different learning-information?].
Would there be any possibility to say "just syncronise the learning information" and on the other side when importing cards to take the (new) card's information and don't mark cards as changed when only the tag has changed ?
See comments for workaround.
-
Angelika Blaschka commented
o.k., I'll keep in mind to call, if it happens again (at the moment all five databases are without duplicates and fine).
-
Strange, if that's indeed what's happening, you should get conflicts on the next sync, and not duplicate cards appearing.
Perhaps if this happens again in the future, have a closer look at the circumstances, because perhaps something else is going on.
-
Angelika Blaschka commented
getting clearer ...
while updating the children's databases they don't have their phones (and are _VERY_ sorry about not beeing able to use memosyne *g*)
'duplicates' means here: when I started "find duplicates" within the child's database on the desktop, it found two cards, one with the original tag and one with the actual tags. Also it found cards where I added additional meanings or clearified some text. (Both with different learning information). I always use *.cards-format and sync is always started by the phone.
Unfortunately I can't tell the kids to stop learning while I edit all the cards / tags and I suppose, that's the moment, that causes the problem, when the children memorise cards I had to change in the meantime (= since the last roll-out to the children's phones).
Most of the changes just concern the tags and that was the reason for adding my idea, that adding a tag should just create a "put it into an additional folder" and not "card is changed". -
What you describe should work, and is quite similar to what I do, provided you tell the kids to not touch their phones while you are doing the edits, and that they sync before they start learning again after you are finished.
But perhaps there is still a miscommunication. What exactly do you mean by 'duplicates'? Are you talking about sync conflicts where Mnemosyne asks you in which direction to perform a full sync? Or are you talking about two similar cards being generated? Provided you export and import using the *.cards format, this should update existing cards as opposed to creating new cards.
-
Angelika Blaschka commented
o.k., here's the long version ;-):
I have one "master-database" with just the cards without learning information. Cards are tagged with the learning-years, child_learn_now and (school-)subject. Not-Knowing a word by working through the school-books creates the request to add a card/add a tag/change a card (e.g. with additional meanings). All changes are done only in the master-db. Always all cards are exported.
Children learn on their phones, synchronised with their databases. In each of the child's database I first synchronise (to get the learning information), import the (changed) cards [and here's the point where in my opinion duplicate cards arise], review the correct activating of the cards [for each child the right school-year ;->] and synchronise with the child's phone to receive the newest status and children continue to memorise.
So unfortunately changing and learning occure parallel here. -
Not sure I understand how the fact that you have more children comes into play here.
Can you perhaps explain in a bit more detail how and where you add the tags and when exactly this results in duplicates?
-
Angelika Blaschka commented
O.k., answer as suspected. The way you described works perfect in a single-user-environment, but here I won't stop four children learning their vocabulary while I change the cards ;->
So I'll keep on deleting duplicate cards once or twice a year.
Thanks. -
Having the option to selectively sync only part of the information would be a recipe for disaster, so that's a no-go, I'm afraid.
However, I'm a bit confused, because in this scenario, adding tags to only one database should be certainly be possible. You only have to make sure that you don't 'touch' the same card on two devices between syncs. E.g., you cannot sync, then review a card on the phone, then add a tag to this card on the desktop, and then sync again. It has to be sync, add tag, sync, review card, sync.