Host SDD primer again

[larsgw]

I was wondering if there was interest to host the SDD primer again. It's currently archived in the twiki format (e.g. https://github.com/tdwg/wiki-archive/tree/master/twiki/data/SDD/Primer), but this is difficult to read, especially the tables and images. I made a script to convert the twiki content to HTML for personal use (https://larsgw.github.io/tdwg-wiki-archive/SDD/Primer/SddIntroduction.html). Is there interest for me to clean up that HTML (some links are broken) and host it here?

[stanblum]

Hi Lars, Yes, I would be interested in posting a copy of your resurrected SDD Primer. I'm not sure it should go on the TDWG website; because the TDWG website repo actually has very little information about standards; only the "landing page." The more appropriate place is probably the SDD GitHub repository. We could put a link to it on the SDD landing page, which is on the TDWG website. Would that be acceptable? The two primary movers behind SDD were Gregor Hagedorn and Bob Morris. Sadly, Bob passed away a few years ago (and is very missed in TDWG), and the next steps in Gregor's career path pulled him away from TDWG. I'm curious about your interest in SDD. Are you using it yourself (and how?), and are you aware of others who are using it? Last, is the script you wrote "generic", in that we could run it on other content that we "lost" when the Twiki collapsed? What is the script written in? In any event, thank you very much for your efforts in resurrecting the SDD Primer.

…

-Stan

On Thu, Feb 2, 2023 at 6:10 AM Lars Willighagen ***@***.***> wrote: I was wondering if there was interest to host the SDD <https://www.tdwg.org/standards/sdd/> primer again. It's currently archived in the twiki format (e.g. https://github.com/tdwg/wiki-archive/tree/master/twiki/data/SDD/Primer), but this is difficult to read, especially the tables and images. I made a script to convert the twiki content to HTML for personal use ( https://larsgw.github.io/tdwg-wiki-archive/SDD/Primer/SddIntroduction.html). Is there interest for me to clean up that HTML (some links are broken) and host it here? — Reply to this email directly, view it on GitHub <#487>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACKZUDKXSXCVUKMH2SNRXH3WVO54TANCNFSM6AAAAAAUPCMPLQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[larsgw]

Hi Stan,

The more appropriate place is probably the SDD GitHub repository. We could put a link to it on the SDD landing page, which is on the TDWG website. Would that be acceptable?

Yes, definitely.

I'm curious about your interest in SDD.

I am working on a platform for curating a collection of identification keys and similar resources (https://identification-resources.github.io/). I am already using Darwin Core for data on the taxonomic scope of the keys. In some cases I would like to save keys in a standard format for archival and display, especially those that are hard to access otherwise.

Are you using it yourself (and how?), and are you aware of others who are using it?

I know that Xper³ uses a modified version of SDD for their identification key platform. Personally, I recently used SDD when helping an organization recover an interactive multi-access key from an old relational database that they could no longer run, and I delivered this as an SDD file compatible with Xper³. However, I ran into some limitations of the format (mostly missing characteristic types for spatial and temporal data), and I feel like there's good potential to make SDD more interoperable with other TDWG standards such as Darwin Core.

Last, is the script you wrote "generic", in that we could run it on other content that we "lost" when the Twiki collapsed? What is the script written in?

Yes, the other content is also online but generally contains more errors (e.g. https://larsgw.github.io/tdwg-wiki-archive/Main/BioBlitz2010). I can work on refining the script some more. It is written in JavaScript (source) and also uses a GitHub Actions workflow to copy static files (source).

[stanblum]

Thank you for all that. Good to know! It looks to me like the place to put the Intro/Primer would be in the "code" of SDD repository, and then replace the link to it from the main SDD repo page: https://www.tdwg.org/standards/sdd/ Would you like to make a pull request to that repo, or would you rather send me the file(s)?

…

On Thu, Feb 2, 2023 at 12:56 PM Lars Willighagen ***@***.***> wrote: Hi Stan, The more appropriate place is probably the SDD GitHub repository. We could put a link to it on the SDD landing page, which is on the TDWG website. Would that be acceptable? Yes, definitely. I'm curious about your interest in SDD. I am working on a platform for curating a collection of identification keys and similar resources (https://identification-resources.github.io/). I am already using Darwin Core for data on the taxonomic scope of the keys. In some cases I would like to save keys in a standard format for archival and display, especially those that are hard to access otherwise. Are you using it yourself (and how?), and are you aware of others who are using it? I know that Xper³ <https://www.xper3.fr/> uses a modified version of SDD for their identification key platform. Personally, I recently used SDD when helping an organization recover an interactive multi-access key from an old relational database that they could no longer run, and I delivered this as an SDD file compatible with Xper³. However, I ran into some limitations of the format (mostly missing characteristic types for spatial and temporal data), and I feel like there's good potential to make SDD more interoperable with other TDWG standards such as Darwin Core. Last, is the script you wrote "generic", in that we could run it on other content that we "lost" when the Twiki collapsed? What is the script written in? Yes, the other content is also online but generally contains more errors (e.g. https://larsgw.github.io/tdwg-wiki-archive/Main/BioBlitz2010). I can work on refining the script some more. It is written in JavaScript ( source <https://github.com/larsgw/tdwg-wiki-archive/tree/master/script>) and also uses a GitHub Actions workflow to copy static files (source <https://github.com/larsgw/tdwg-wiki-archive/blob/master/.github/workflows/static.yml> ). — Reply to this email directly, view it on GitHub <#487 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACKZUDJMO6HTGZZTWWWZCXTWVQNOVANCNFSM6AAAAAAUPCMPLQ> . You are receiving this because you commented.Message ID: ***@***.***>

[baskaufs]

Hi Stan and Lars,

What needs to happen is for the generated HTML to be put some stable place where it’s going to get rendered into a GitHub pages web page. If it just gets put into the code of the SDD repository without that repository being set up with GitHub pages, it won’t be rendered as a web page. People will just see the HTML markup.

@peterdesmet would it make sense to just enable GitHub Pages for the SDD repo and have it point to a docs directory or something. The generated HTML page could be the only thing that lives there. Once it's getting rendered, it could be linked from the Standards landing page as Stan suggested.

[stanblum]

Good point, @Steve Baskauf ***@***.***>. Thanks for that correction!

…

On Thu, Feb 2, 2023 at 2:21 PM Steve Baskauf ***@***.***> wrote: Hi Stan and Lars, What needs to happen is for the generated HTML to be put some stable place where it’s going to get rendered into a GitHub pages web page. If it just gets put into the code of the SDD repository without that repository being set up with GitHub pages, it won’t be rendered as a web page. People will just see the HTML markup. @peterdesmet <https://github.com/peterdesmet> would it make sense to just enable GitHub Pages for the SDD repo and have it point to a docs directory or something. The generated HTML page could be the only thing that lives there. Once it's getting rendered, it could be linked from the Standards landing page as Stan suggested. — Reply to this email directly, view it on GitHub <#487 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACKZUDKTQU32GDNDE3I6PH3WVQXQFANCNFSM6AAAAAAUPCMPLQ> . You are receiving this because you commented.Message ID: ***@***.***>