Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
How to organize student submissions
andy_mundell620
Member Posts: 4 EDU
Does anybody have any tips for organizing student submissions. Typically I have them share their project with me, and then I have to manually go in and add labels or create folders and then move them. This can be time consuming, and is easy to lose track of assignments (especially those submitted early or late). Is there a way for students to submit something already labeled or directly to a specific folder?
0
Comments
I require a specific naming convention for all student assignments. I tell them that just like in industry "if I cannot find your work, it does not exist." I use the following convention: "M1 bradyb Hole Tool Practice"
The first portion is the specific assignment code that I have assigned, i.e. M1 is for modeling assignment 1 whereas P1 would be used for project 1. Next is the students username, i.e. their school email less the @university.edu part. Lastly is the topic of the assignment. That part is more for them to easily identify what should be in any specific document in their list.
I then search in the "shared with me" area for the assignment code. If a student did not use the code, it does not exist. They can always rename the document if they miss the code and let you know so you can find it. Once the search is complete I select all of the documents shown and apply a tag so I can grade later. I add a second tag called "Graded" after reviewing and commenting on a document so I know what I have left to do.
I hope this helps.
Twitter: @bradleysauln
- the ability to view my folders under files created by me.
- the ability to sort teams I've created vs teams I've been added to.
- the ability to create a team that I use to share files out, but other team members can't.
I think there is more, but this is good, for now.1. Bulk remove from share
2. Ability to find "shared with me" that are not tagged
- allow me to write a description or even attach a rubric for what they should be submitting
- automatically place student submissions into a folder
- a timestamp for when the file was submitted, or ability to not accept submissions after a certain time
- automatically place a folder specific tag onto all submissions into that folder
- lock students out of modifying their file after submission.
I recently gave an exam where students were required to model a part within the time frame. We were able to identify students who cheated when we noticed a shared mistake between both files and then examined timestamps. One student had created the part, shared it with another student, and then they made a copy and submitted it. With the second file created after the first file had last been edited, it was obvious, but there are many other ways to cheat that would be harder to detect.
Creating a part template that is not allowed to be shared with anybody but the instructor (or some other way of identifying the origin of a part studio) would be huge. In the future I plan on creating all of the individual part studio templates, share them with students, and not give them the ability to invite collaborators, but this will be time consuming.
History is your friend. I peruse the history often, especially if something seems fishy.
I require my students to create a version with a specific naming convention as well as name their document a specific way. Except early in the semester when they are getting used to both Onshape and me, I enforce a "no version, no grade" policy. When grading, I branch their version if there are changes made since the version was created and grade the branch, otherwise I grade "Main". This ensures that I am only grading what they "submitted" before the due date/time. I also always check to see that the version was created before the due date.
https://forum.onshape.com/discussion/comment/51281#Comment_51281
I am also curious if any instructor provides grading feedback via comments?
I have also thought of using teams to divide your students into classes to distribute assignments, by creating a document with the assignment information and sharing to the team. Remember documents can contain more than just CAD models! This might make it easier to reset after new classes start. You can just update the team members- remove the old students, and add the new.
You could also use teams if students work on projects together in a group, you could add all the students in a group to each team, to make it easy for them to share/work on the right documents together. If you create the team- you would have more insight into how their projects are coming along (as long as they share the docs with the team- because you would be part of the team).
To turn in an assignment, I think its good to have the student share to the instructor/TA, if they shared to the team- then all other students would be able to see their work.
The idea to use labels to mark what you have graded seems like a great idea- since its specific to you and not the students.
These are just some ideas I have had to make use of some of these professional tools in Onshape in a classroom environment- and would like some feedback from you guys if you think any of these are viable or could work in your classrooms.
HWM-Water Ltd
I always check to see to see if there are any changes after the version. If there are, I activate the version and grade it, leaving comments. If there are no changes after versioning, I just grade Main.
Brian
M1_Seed
Then I write a script using an API (assuming it can be done) to copy the seed file, rename it to follow convention, and share it with the student. For example, if I had a list of student1@abc.edu and student2@abc.edu I could have the script generate 2 copies of the seed file named . M1_student1 and M1_student2 and then share the appropriate file with them via their email address.
Not sure if the API would support this or not (haven't looked) but seems like a pretty basic process that should be doable. If it would help anyone I will try to find time to experiment a bit with it.