Bugs from testing RO-Crate creation

[rosanna-smith]

These are some of the bugs/questions River, Otis and I ran into creating an RO-Crate for the Deafblind corpus (using the mode Language Data Commons top level Collection (corpus):

• @id defaults to ./ - is this something that needs to be edited (add DOI here?) or should that remain as is? Not clear currently.
• Collection Description help text says max 200 word limit, though our description exceeded this and still saved, so assume this is more guidance than a set rule?
• The red property required information icons look more like errors, so even when we'd filled these sections, it seems like there's a problem when there's not. Another colour might be better.
• When creating people, e.g. authors etc. should the ORCID be included in the description or is there another section for this?

[r-tae]

Also there's a field 'Citation', the description is "Associated publications". I have a list of publications that reference the corpus, is this the proper place for that?

Never mind, Rosanna sent me documentation about it on Slack

[r-tae]

Re: the organisation lookup

I checked on my local version (up-to-date with main), there is debouncing its just the lookup can take up to 15s, which means just debouncing isn't enough.

You can see in my example that the middle request resolves last and I end up with no monash results.

It would be fixable if we could cancel in-flight requests, but I don't understand the code well enough to do that (and promises aren't cancellable by themselves so it isn't a particularly quick change)

[rosanna-smith]

Question about this section @ptsefton: When creating people, e.g. authors etc. should the ORCID be included in the description or is there another section for this?

I checked the language data commons top level and for author we have @id, @type, Name and Description. Should the ORCID go in the description field or in @id? The tooltip for @id just says Uniquie ID, but it's not one of the tooltips I can edit in the mode.

[ptsefton]

ORCID if available should go in @id for people

…

-- From: Rosanna ***@***.***> Date: Thursday, 16 May 2024 at 11:21 am To: Language-Research-Technology/crate-o ***@***.***> Cc: Peter Sefton ***@***.***>, Mention ***@***.***> Subject: Re: [Language-Research-Technology/crate-o] Bugs from testing RO-Crate creation (Issue #125) Question about this section @ptsefton<https://github.com/ptsefton>: When creating people, e.g. authors etc. should the ORCID be included in the description or is there another section for this? I checked the language data commons top level and for author we have @id<https://github.com/id>, @type<https://github.com/type>, Name and Description. Should the ORCID go in the description field or in @id<https://github.com/id>? The tooltip for @id<https://github.com/id> just says Uniquie ID, but it's not one of the tooltips I can edit in the mode. — Reply to this email directly, view it on GitHub<#125 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAFYTWCWRLQ3ZMZCIAM4F3DZCQCX7AVCNFSM6AAAAABHN453MWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJTG4ZTEMRYGE>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ptsefton]

We may need to get our own copy of the ROR data and provide a faster lookup

…

-- From: River ***@***.***> Date: Thursday, 9 May 2024 at 11:21 am To: Language-Research-Technology/crate-o ***@***.***> Cc: Peter Sefton ***@***.***>, Assign ***@***.***> Subject: Re: [Language-Research-Technology/crate-o] Bugs from testing RO-Crate creation (Issue #125) Re: the organisation lookup I checked on my local version (up-to-date with main), its just the lookup is very slow (on my network at least) and it doesn't cancel in-flight requests if you type more. You can see in my example that the middle request resolves last and I end up with no monash results. CleanShot.2024-05-09.at.11.15.44.gif (view on web)<https://github.com/Language-Research-Technology/crate-o/assets/22485304/b8136df4-d7b2-4b05-a66a-52833cdf5e7e> — Reply to this email directly, view it on GitHub<#125 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAFYTWCAKCNDKTJ3DL6EZSTZBLFSNAVCNFSM6AAAAABHN453MWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRG42TKMBVHA>. You are receiving this because you were assigned.Message ID: ***@***.***>

[ptsefton]

Yes

…

-- From: River ***@***.***> Date: Thursday, 9 May 2024 at 10:57 am To: Language-Research-Technology/crate-o ***@***.***> Cc: Peter Sefton ***@***.***>, Assign ***@***.***> Subject: Re: [Language-Research-Technology/crate-o] Bugs from testing RO-Crate creation (Issue #125) Also there's a field 'Citation', the description is "Associated publications". I have a list of publications that reference the corpus, is this the proper place for that? — Reply to this email directly, view it on GitHub<#125 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAFYTWHEYATMXIOHV4XC43DZBLCWPAVCNFSM6AAAAABHN453MWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRG4ZTINJUGY>. You are receiving this because you were assigned.Message ID: ***@***.***>

[r-tae]

Perfect, thanks @ptsefton ! I believe I have enough to finalise both the Australian Deafblind Signing and Auslan Corpora

[rosanna-smith]

Marking as closed since @alvinsw will be updating the description of the @id in Crate-O. (thanks!)