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

Preserved Height box bug? #2948

Closed
maychu16 opened this issue Nov 1, 2024 · 6 comments
Closed

Preserved Height box bug? #2948

maychu16 opened this issue Nov 1, 2024 · 6 comments
Assignees

Comments

@maychu16
Copy link

maychu16 commented Nov 1, 2024

The excavator's note has texts for the preserved height. When I typed them in, I noticed that the recording app turned them into numbers only. But I can see the notes I typed in if I clicked the box. Not sure if it is a bug or if I am not supposed to type texts in there.

Screenshot 2024-10-31 at 11 54 42 PM Screenshot 2024-10-31 at 11 54 34 PM
@maychu16 maychu16 added 🐞 bug Something isn't working new-issue issue needs to be reviewed and labels and projects need to be added. Remove afterwards. labels Nov 1, 2024
@urapadmin
Copy link
Collaborator

recording 16.2.5, rolled out to BUAP on 1.XI.24 11:00 pm

I copy @liviah848 here to spread the information. (I guess I should make a BUAP group)

it was the same with wall thickness: FileMaker allows inputting text in numerical fields by default. Drives me nuts. And then Kiosk would eradicate everything that isn't a number.

  • I have limited both fields explicitly to mere numerical inputs in FileMaker.
  • brick size and stone size have been and keep being text fields because they are famous for having all kinds of inputs

The question that remains is where to put the narrative: Please discuss it with @lbestock I also wonder if the fields we have here should be extended or refined. E.g. nobody would have a clue about what units of measurements to use here.

@urapadmin urapadmin added this to the recording app 17 milestone Nov 1, 2024
@urapadmin urapadmin removed the new-issue issue needs to be reviewed and labels and projects need to be added. Remove afterwards. label Nov 1, 2024
@urapadmin urapadmin added this to testing Nov 1, 2024
@github-project-automation github-project-automation bot moved this to Needs triage in testing Nov 1, 2024
@luizaogs
Copy link
Collaborator

luizaogs commented Nov 3, 2024

This is working as you outline above. Since it still seems to require discussion, I won’t close it but I will remove it from testing.

@luizaogs luizaogs removed this from testing Nov 3, 2024
@urapadmin
Copy link
Collaborator

@lbestock Another reminder that that might need your attention.
For me it is done and so I close this

@luizaogs
Copy link
Collaborator

luizaogs commented Nov 4, 2024

For what it’s worth Lutz, and since you still have room in the layout, a “further observations on measurements” text field (similar to what we did for CM) or something could be useful. I only chime in because it is something that could have been useful for MADP too but I think we just ended up adding notes to the general locus observations since they didn’t fit here.

@urapadmin
Copy link
Collaborator

which was the right place to put it right now, I think.
The downside of too many description fields in several places might be that information gets a bit scattered and it gets harder to get the whole picture. But I thought a free input in the architecture layout cannot hurt.
However, I before I extend the architecture layout I want to hear what BUAP and Abydos actually need. There might be more ...

@urapadmin
Copy link
Collaborator

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

No branches or pull requests

3 participants