Just as the bios generator automatically creates IDs for speakers based on their last names, I'd like the schedule generator to automatically link people's names to their bios. I recognize that it's probably overkill to actually have the schedule template somehow read the speakers source markdown file to check the speaker exists, so I think that it should just create links with the assumption that there is a file called speakers.html in the same directory as the generated sessions file, and that the speaker exists in the file.
It can determine the ID to put in the URL based on the speaker's name, using the same algorithm that the speakers template uses to generate the ID. However, there is a possibility for mistakes if there are two speakers with the same last name that appear in different orders in the two documents.
Because of this, I think that if we go with this solution, we should add the ability to write some kind of code into the sessions source markdown file to override the speaker ID that's created by the sessions template for a given speaker. Since we currently don't have any speakers with the same name, this override capability can come after the automatic link generation is implemented. (Also, if you can think of a better way to do this, that's awesome -- I just wanted to clarify my thoughts).
Just as the bios generator automatically creates IDs for speakers based on their last names, I'd like the schedule generator to automatically link people's names to their bios. I recognize that it's probably overkill to actually have the schedule template somehow read the speakers source markdown file to check the speaker exists, so I think that it should just create links with the assumption that there is a file called speakers.html in the same directory as the generated sessions file, and that the speaker exists in the file.
It can determine the ID to put in the URL based on the speaker's name, using the same algorithm that the speakers template uses to generate the ID. However, there is a possibility for mistakes if there are two speakers with the same last name that appear in different orders in the two documents.
Because of this, I think that if we go with this solution, we should add the ability to write some kind of code into the sessions source markdown file to override the speaker ID that's created by the sessions template for a given speaker. Since we currently don't have any speakers with the same name, this override capability can come after the automatic link generation is implemented. (Also, if you can think of a better way to do this, that's awesome -- I just wanted to clarify my thoughts).
Hm, I just noticed that the person creating the program has started putting speaker's organizational affiliations into the session descriptions, in addition to their names. Keep that in mind. We could probably remove the affiliations in the session descriptions if need be, but it seems like a good idea to keep them.
Hm, I just noticed that the person creating the program has started putting speaker's organizational affiliations into the session descriptions, in addition to their names. Keep that in mind. We could probably remove the affiliations in the session descriptions if need be, but it seems like a good idea to keep them.
Just as the bios generator automatically creates IDs for speakers based on their last names, I'd like the schedule generator to automatically link people's names to their bios. I recognize that it's probably overkill to actually have the schedule template somehow read the speakers source markdown file to check the speaker exists, so I think that it should just create links with the assumption that there is a file called speakers.html in the same directory as the generated sessions file, and that the speaker exists in the file.
It can determine the ID to put in the URL based on the speaker's name, using the same algorithm that the speakers template uses to generate the ID. However, there is a possibility for mistakes if there are two speakers with the same last name that appear in different orders in the two documents.
Because of this, I think that if we go with this solution, we should add the ability to write some kind of code into the sessions source markdown file to override the speaker ID that's created by the sessions template for a given speaker. Since we currently don't have any speakers with the same name, this override capability can come after the automatic link generation is implemented. (Also, if you can think of a better way to do this, that's awesome -- I just wanted to clarify my thoughts).
Hm, I just noticed that the person creating the program has started putting speaker's organizational affiliations into the session descriptions, in addition to their names. Keep that in mind. We could probably remove the affiliations in the session descriptions if need be, but it seems like a good idea to keep them.
The script can auto-link speakers in the schedule MD. See https://pypi.python.org/pypi/lpschedule-generator#auto-linking-speaker-names