-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
[NAT-4] NAT Rooms #495
[NAT-4] NAT Rooms #495
Conversation
…ep the names defined in the areatree; I verified by hand that the names from the NAT roomfinder do not contain more information than what we have already. They are mostly from the MyTUM Roomfinder)
This is finished mostly. Only three things are missing currently:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are some preliminary things I have found.
I have to look into the code a bit deeper, as there are some things (some code paths+how it looks in the frontend) I would like to investigate
) | ||
|
||
|
||
def _is_room_excluded(internal_id, b_id, data): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a Docstring (imo this function does a bit of magic which I don't fully understand why yet)? 😅
return True | ||
|
||
|
||
def _get_room_base(internal_id, b_id, nat_data, data, usages): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a Docstring (you can probably betterdescribe what this function does)? 😅
data/processors/nat.py
Outdated
if len(building_sources) == 2 and building_sources[1]["name"] == "NAT Roomfinder": | ||
return False | ||
|
||
return True |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if len(building_sources) == 2 and building_sources[1]["name"] == "NAT Roomfinder": | |
return False | |
return True | |
return len(building_sources) != 2 or building_sources[1]["name"] != "NAT Roomfinder" |
|
||
|
||
def _merge_nat_extra_props(r_data, nat_data): | ||
# pylint: disable=too-many-branches |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are many branches, can we extract something into its own method?
I think infrastructure
(seating, streaming, sockets) would be fitting
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
About the frontend-changes (here and not inline commented, to keep things more dense):
- I would prefer
alternative Seating Configurations
Seating Plan
- I would the seating to be displayed as a list. given that this is an eazy fix we can also postpone this one into another PR if you'd like
- I would prefer
Straming avalible via ...
as a link text for hörsaal.webcam and linking totum.live/about
instead of the wiki entry for the RBG
What do you think?
I used a comma because it seems a list needs a change in the frontend (I tried to at least use
Given that only a handful of rooms have this property, should we rather add the data outselves in |
Co-authored-by: Frank Elsinga <frank@elsinga.de>
I am going to close this due to the high amount of merge conflict. I don't think navigatum should show the extended seating information as TUM has bought the TUMexam service pack and this is one of the things they do. The other information (e.g. extra rooms) has somewhat dubeous data quality and is thus quite hard to merge.. I don't have a good solution on this one. |
Resolves #34
Proposed Changes (include Screenshots if possible)
How to test this PR
How has this been tested?
Checklist: