Participant ID

Wed Aug 11 17:01:06 UTC 2021

Dear Leonid and Brian,

I cannot thank you enough for the help. Thanks for the clear explanations
and instructions.

Thank you,
Elnaz

Elnaz Kia, Ph.D. (she, her, hers)

*Post-Doctoral Research Associate
<https://l2trec.utah.edu/about/staff-directory.php>*

Second Language Teaching and Research Center (L2TReC)
<https://l2trec.utah.edu/>

University of Utah

LinkedIn
<https://www.linkedin.com/in/elnaz-kia?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base_contact_details%3B%2FResGVF2SMGMAxhocdPnRw%3D%3D>

Personal Website <https://elnazkia.weebly.com/>

On Wed, Aug 11, 2021 at 9:38 AM Brian Macwhinney <macw at andrew.cmu.edu>
wrote:

> Leonid,
>     Thanks for pointing this out.  Yes, this is totally correct.
> — Brian
>
> > On Aug 11, 2021, at 12:36 PM, Leonid Spektor <spektor at andrew.cmu.edu>
> wrote:
> >
> > There is another reason to keep speaker codes simple and uniform. Some
> commands require specifying speaker code with +t option to run analyses on
> data files. If you have many different speaker codes, such as c0002, c0003,
> c0004 and so on, then when you run commands on multiple data files, for
> example *.cha, you will have to use +t option to specify all different
> speaker codes that you have in your data files. The best solution would be
> to have one consistent *STU: code for all students and the way you can
> distinguish one subject from another is by filename or by @ID code. This
> way you can run command like KWAL or FREQ on *.cha with just one +t*STU
> option. You can edit @ID headers with "Tiers->ID headers" menu.
> >
> > For example your data file would look like this:
> >
> > @Begin
> > @Languages:   zho
> > @Participants:        STU IDc0002 Student
> > @ID:  zho|corpus|STU|0;00.00||||Student||IDc0002|
> > @Media:       c0002cadr01_1, audio
> > @Transcriber: Xiqiang Wang
> > @Comment:     hum, ahn, ah, eh signal hesitation
> > @Situation:   unspecified
> > *STU: eh (..) .
> > *STU: wo3 (..) .
> > *STU: eh .
> > @End
> >
> >
> > Leonid.
> >
> >> On Aug 11, 2021, at 11:26, Brian Macwhinney <macw at andrew.cmu.edu>
> wrote:
> >>
> >> Dear Elnaz,
> >>   Leonid pointed out that your IDs are technically okay.  However,
> unless you really envision recruiting 10,000 participants, I think it would
> be much better to stick with two digits for the subject ID and maybe
> consider whether the inclusion of “c” is really necessary.  Perhaps it is
> redundant with something else?  So, maybe you only need *02 and such.
> >>
> >> — Brian MacWhinney
> >>
> >>> On Aug 11, 2021, at 3:22 AM, Elnaz Kia <ek325 at nau.edu> wrote:
> >>>
> >>> Hello again,
> >>>
> >>> I had a question about the participant ID in CHAT. In our corpus, all
> the files are single-speaker and the participant ID includes 5 characters,
> one letter representing the language, and 4 digits representing a unique
> student id).
> >>>
> >>> @Begin
> >>> @Languages: zho
> >>> @Participants: c0002 IDc0002 Student
> >>> @ID: zho|corpus|c0002|0;00.00||||Student|||
> >>> @Media: c0002cadr01_1, audio
> >>> @Transcriber: Xiqiang Wang
> >>> @Comment: hum, ahn, ah, eh signal hesitation
> >>> @Situation: unspecified
> >>> *c0002: eh (..) .
> >>> *c0002: wo3 (..) .
> >>> *c0002: eh .
> >>> @End
> >>>
> >>> According to the CHAT Manual (2021, p. 21), "After the asterisk on the
> main line comes a three-letter code in upper case letters for the
> participant who was the speaker of the utterance being coded."
> >>>
> >>> My questions are:
> >>> 1. How does the fact that our participant IDs are 5 characters and
> include digits affect CLAN functions?
> >>> 2. If having more than 3 characters is okay, does it matter whether
> the letters are capital or small (c0002 vs. C0002)? Which one is preferred?
> >>>
> >>> I would appreciate any help!
> >>>
> >>> Thanks,
> >>> Elnaz
> >>>
> >>>
> >>> Elnaz Kia, Ph.D. (she, her, hers)
> >>> Post-Doctoral Research Associate
> >>> Second Language Teaching and Research Center (L2TReC)
> >>> University of Utah
> >>> LinkedIn
> >>> Personal Website
> >>>
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> Groups "chibolts" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send
> an email to chibolts+unsubscribe at googlegroups.com.
> >>> To view this discussion on the web visit
> https://groups.google.com/d/msgid/chibolts/CAOwOJYneWMKtfh8tqzT80Fh8WDEroe6TKC8qyuPuByiQnXXh2w%40mail.gmail.com
> .
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups "chibolts" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an email to chibolts+unsubscribe at googlegroups.com.
> >> To view this discussion on the web visit
> https://groups.google.com/d/msgid/chibolts/4B98B1BA-24CA-4739-B0DA-A45737A175E4%40andrew.cmu.edu
> .
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "chibolts" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to chibolts+unsubscribe at googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/chibolts/CB9C77A2-9F2C-4A6B-8A6D-F7A5F8F002FF%40andrew.cmu.edu
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "chibolts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to chibolts+unsubscribe at googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/chibolts/369C320B-CFA7-49F1-9D48-FD948D4C6CFC%40andrew.cmu.edu
> .
>

-- 
You received this message because you are subscribed to the Google Groups "chibolts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chibolts+unsubscribe at googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chibolts/CAOwOJYkk%3DbGvUcTR4uOr8KZMrc%3DuWCZNGWPD8nqszbhUMgh11w%40mail.gmail.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.linguistlist.org/pipermail/chibolts/attachments/20210811/5fc7fcaa/attachment.htm>