-
Notifications
You must be signed in to change notification settings - Fork 0
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
recording app: make new OP from archival entity #3015
Comments
That's not possible simply because a unit needs a lot of information before it can be created. That's why the layout for adding a unit is so big and complicated. I can send you to that layout, but I don't think that's exactly what would help you, would it? |
It would be at least a little easier. No, I see what you mean. I end up not putting in all the information for the unit, because I don’t know it at the time I am creating it. I mean the absolute dream is totally impossible, it is that I just write the OP numbers, and then when those OPs end up being created later the link would just appear there. Sort of like the ANC data gets imported with seeming magic once the relevant locus and lot are created. But I say it just so you can see what it is that would help, not because I think it’s a reasonable request. |
Ja, that would be so extremely tailored to your just-now use case that I must refuse. I am not entirely sure what the point of the units list is anyways. Jumping there? |
Oh yes. Navigation. Then we could just do away with that tab, even. I have been just naturally putting the OPs in the description anyway. Navigation there would be perfect. |
recording app 16.7.2
|
It really would be helpful to be able to create OPs in the OP link section, same way we can create loci in the relations. I am usually creating a record for stuff that has not been put in yet. So the OPs usually don’t exist. I have to exit, create the OPs, then go back and link them. This is a step I find I often skip because it is cumbersome, but that’s some of the most important information.
The text was updated successfully, but these errors were encountered: