--
You are subscribed to the publicly accessible group "FLEx list".
Only members can post but anyone can view messages on the website.
To change your status, please write to flex_d...@sil.org.
You can join this group by going to http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/b27d4661-0f73-4c9f-a9db-7f30d8ba4bfc%40googlegroups.com.
Hi Mike,
Back in 2014, 2015, this repository (byw-dictionary) was loaded with LIFT data. That’s why you get the ‘Common Revision’ error if you try to load it for the first time. It already contains data. After you do the ’Get Project from Colleague’ command, notice that the ‘Send/Receive Lexicon (WeSay)’ command is available. This type of repository is intended for use with LIFT (WeSay) data. There should be one FLEx user that keeps this repository in sync with FLEx data. If you want a FLEx repository, you can request one at ad...@languagedepot.org. The required information to get a repository created in on the home page at public.languagedepot.org. If you want to get the byw-dictionary repository cleared out so you can start again, send me a message at ad...@languagedepot.org.
I hope this helps!
Ann
--
To unsubscribe from this group and stop receiving emails from it, send an email to flex...@googlegroups.com.
Hi Mike,
This is definitely a LIFT (WeSay) project. It was created that way. I add Dictionary after the project name and ID if that is what was requested. It was also loaded with LIFT data. That is, lexicon only data (no texts) and formatted for sharing with programs that support the LIFT protocol such as WeSay an Lexique Pro.
Flex projects share all the data in a FLEx project and this format is more robust. If you are not using this repository with a program (such as WeSay or Lexique Pro) that uses the LIFT protocol, you should probably request a FLEx repository.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/aa654bab-b69f-48a2-9796-5d69ced4dc60%40googlegroups.com.
I would just like to reinforce what Ann wrote: “If you are not using this repository with a program (such as WeSay or Lexique Pro) that uses the LIFT protocol, you should probably request a FLEx repository.” [strike-through is my edit].
My rationale: The Backup/Restore functionality in FLEx is seriously diminished or altered when a project is set up to be shared via Send/Receive. The S/R repository on LanguageDepot.org becomes in essence the project’s backup storage location. If S/R involves only LIFT data, the non-LIFT data in the project are not being “backed up” via Send/Receive. If no one on the team is using WeSay or Lexique Pro to enter or edit data, I see no reason to be doing S/R with anything less than 100% of the data in the project.
That’s my opinion, for what it’s worth. Ann is your go-to person for all questions related to LanguageDepot.org. She has helped me with many projects and gets a 5-star rating from me.
-Kevin
From: flex...@googlegroups.com [mailto:flex...@googlegroups.com] On Behalf Of Mike B
Sent: Tuesday, August 20, 2019 2:54 AM
To: FLEx list <flex...@googlegroups.com>
--
You are subscribed to the publicly accessible group "FLEx list".
Only members can post but anyone can view messages on the website.
To change your status, please write to flex_d...@sil.org.
You can join this group by going to http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/949ea817-f939-41e3-ba2d-1f8d209d5bfb%40googlegroups.com.