Workshop 5B, Jaquet/Chau

[mtwente]

Pull request

Proposed changes

• add short description of the workshop offered by Daniel Jaquet and Tsz Kin Chau
• closes Add Workshop 5B #82

Co-authored-by: Daniel Jaquet [email protected]
Co-authored-by: Tsz Kin Chau [email protected]

Types of changes

• New feature (non-breaking change which adds functionality).
• Enhancement (non-breaking change which enhances functionality)
• Bug Fix (non-breaking change which fixes an issue).
• Breaking change (fix or feature that would cause existing functionality to change).

Checklist

• I have read the README document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have mentioned all co-authors in the PR description as Co-authored-by: Name <[email protected]>.

Summary by CodeRabbit

• New Features
  • Updated "Session 5B (Workshop)" entry with a hyperlink for easy access to submission details.
  • Introduced a new manuscript submission titled "Unveiling Historical Depth: Semantic annotation of the Panorama of the Battle of Murten," including detailed metadata and context.
• Documentation
  • Added a configuration file for the manuscript project, specifying project type and output format.

[coderabbitai]

Walkthrough

This pull request introduces updates to the conference schedule and adds new submission details for a workshop. Specifically, it modifies the entry for "Session 5B" to include a hyperlink to a submission page. Additionally, a new manuscript configuration file and an index file for the workshop submission are created, detailing the workshop's metadata and context.

Changes

File Path	Change Summary
conference-program/schedule.qmd	Updated "Session 5B" entry to include a hyperlink to /submissions/873.
submissions/873/_quarto.yml	Created a new configuration file for a manuscript project, specifying project type and output format.
submissions/873/index.qmd	Introduced a new submission for a workshop, including detailed metadata about the workshop and authors.

Possibly related issues

• digihistch24/book-of-abstracts#82: This issue requests the addition of Workshop Session 5B, which aligns with the changes made in this PR to update the conference schedule.

Possibly related PRs

• Submission 462, Hitz/Prada/Vonwiller #7: Similar to the main PR, this PR adds a _quarto.yml configuration file and an index.qmd file for a manuscript project.
• Various minor fixes #10: This PR modifies the _quarto.yml file, relating to the main PR's focus on enhancing document accessibility through hyperlinks.
• Submission 428, Gabi Wüthrich #12: Introduces a _quarto.yml file and an index.qmd file, indicating a commonality in project structure and configuration.
• Submission 474, Moritz Feichtinger #15: Aligns with the main PR's focus on enhancing document structure and accessibility through the introduction of a _quarto.yml file and an index.qmd file.
• Submission 447, Hart et al. #22: Includes addition of a _quarto.yml file and an index.qmd file, paralleling the main PR's update to the conference schedule.
• Submission 486, Chadha/Rashiti/Sibille #60: Introduces an index.qmd file outlining a submission related to historical research, connecting to the main PR's focus on enhancing accessibility.

Suggested labels

submission

🐰 "In the schedule, a link now shines,
For Session 5B, where knowledge aligns.
A manuscript blooms, with details so bright,
Join us for insights, a workshop delight!
With authors to guide, and laptops in tow,
Let's hop into learning, come join the show!" 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3be8f7e and 2dbd323.

📒 Files selected for processing (3)

• conference-program/schedule.qmd (1 hunks)
• submissions/873/_quarto.yml (1 hunks)
• submissions/873/index.qmd (1 hunks)

✅ Files skipped from review due to trivial changes (2)

• submissions/873/_quarto.yml
• submissions/873/index.qmd

🔇 Additional comments (1)

conference-program/schedule.qmd (1)

27-27: LGTM! Verify the submission link.

The addition of the hyperlink to Session 5B enhances the schedule's accessibility. The link format differs from other sessions, but this appears intentional as it's a workshop rather than a regular session.

Let's verify the submission link and ensure the referenced page exists:

✅ Verification successful

Link is valid and content matches the schedule

The submission link /submissions/873 is valid and points to a workshop submission by Daniel Jaquet and Tsz Kin Chau from EPFL. The content matches the schedule entry perfectly:

• The submission is correctly categorized as "Session 5B"
• It's explicitly marked as a workshop
• The authors and their affiliation match
• The content describes an interactive workshop about panorama annotation

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the workshop submission page
# and check for any other references to this submission

# Check if the submission file exists
fd "index.qmd" submissions/873/

# Look for other references to this submission
rg "/submissions/873" --type md --type qmd

Length of output: 128

---

Script:

#!/bin/bash
# Let's verify the submission content and references with corrected commands

# Check the content of the submission file
cat submissions/873/index.qmd

# Look for references without file type restrictions
rg "/submissions/873"

# Check if there are any broken links in Quarto files
rg "(/submissions/\d+)" --type-add 'qmd:*.qmd' -t qmd

Length of output: 2090

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.