Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event's Organizer should be human readable in tess #305

Closed
bryan-brancotte opened this issue Jan 31, 2024 · 12 comments · Fixed by #311 or #314
Closed

Event's Organizer should be human readable in tess #305

bryan-brancotte opened this issue Jan 31, 2024 · 12 comments · Fixed by #311 or #314

Comments

@bryan-brancotte
Copy link
Member

Spotted by @olisand

https://tess.elixir-europe.org/events/4th-workshop-single-cell-sincellte-2022-single-cell-transcriptomics-spatial-and-multi-omics

@bryan-brancotte
Copy link
Member Author

Renderer should be adapted to handle subnode with M2M (here for Single sub node)

@bryan-brancotte
Copy link
Member Author

Then in get_rdf_mapping put something like

organisedByTeams=dict(schema_attr='organizer', _fields=dict(
         name='name',
         url='homepage',
 ), _type="Organization"),

@bryan-brancotte
Copy link
Member Author

Todo : is tess using all organizers ? Seen only one in https://tess.elixir-europe.org/events/bigomics-genomique-comparative-biopolis while multiple when looking at api : https://catalogue.france-bioinformatique.fr/api/event/591/?format=json-ld

@olisand
Copy link
Member

olisand commented Jan 31, 2024

TeSS answer: currently the scraper will probably just take the first or last one.
I added an issue on their main repo.

@olisand
Copy link
Member

olisand commented Feb 13, 2024

Extract multiple organizers (comma-separated) solved on TeSS side: ElixirTeSS/TeSS#914

@bryan-brancotte
Copy link
Member Author

Good news ! I'm keeping the issue open until we observe that the event have indeed multiple organizer

@olisand
Copy link
Member

olisand commented Feb 15, 2024

Absolutely! But even then, this side issue (organizer names should be scrapped instead of object URLs) will not be fixed yet, or am I wrong?

@bryan-brancotte
Copy link
Member Author

Yes, we ill have to include the organizers with additional nodes as it is done with the postal address

@bryan-brancotte
Copy link
Member Author

Applied in prod, can be seen at https://catalogue.france-bioinformatique.fr/api/event/476/?format=json-ld

@olisand I keep it open to follow it everything works with tess now

@olisand
Copy link
Member

olisand commented Jul 15, 2024

@bryan-brancotte Not yet ok on TeSS. Organizer now shows the name of the event, still followed by urls corresponding to organizer(s) instead of organizer name(s). Example here: https://tess.elixir-europe.org/events/introduction-a-l-analyse-de-donnees-transcriptomiques-avec-galaxy

@bryan-brancotte
Copy link
Member Author

Hi @olisand

Applied in prod : https://catalogue.france-bioinformatique.fr/api/event/637/?format=json-ld

Again I keep it open to follow it everything works with tess now

@olisand
Copy link
Member

olisand commented Aug 26, 2024

Hello @bryan-brancotte
It looks good on TeSS, nice job. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants