ipr.cgi

[ietf-svn-bot]

owner:henrik@levkowetz.com resolution_fixed type_task | by henrik@levkowetz.com

---

---

Issue migrated from trac:3 at 2022-03-04 00:29:29 +0000

[ietf-svn-bot]

@henrik@levkowetz.com changed status from new to assigned

[ietf-svn-bot]

@henrik@levkowetz.com changed owner from henrik to henrik@levkowetz.com

[ietf-svn-bot]

@henrik@levkowetz.com changed status from assigned to closed

[ietf-svn-bot]

@henrik@levkowetz.com changed resolution from `` to fixed

[ietf-svn-bot]

@fenner@research.att.com changed status from closed to reopened

[ietf-svn-bot]

@fenner@research.att.com changed resolution from fixed to ``

[ietf-svn-bot]

@fenner@research.att.com commented

---

I noticed a couple of major differences between the cgi and django versions:

• The cgi version displays a preview
• The cgi version displays a message that the disclosure has been submitted and it will be reviewed and posted. The django version sends you directly to your new disclosure, which could allow you to post a link to it before it is reviewed and posted. (Should the view detail say "this is under review" instead of showing the disclousre?)
• The cgi version sends email to the secretariat (in the same general format as the preview) as a notification of the new submission.

If nothing else, the django version should at least send the same kind of email to keep the workflow the same.

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

Replying to ietf-svn-conversion/datatracker#3 (comment:3):

I noticed a couple of major differences between the cgi and django versions:

• The cgi version displays a preview

Missing feature in django version.

• The cgi version displays a message that the disclosure has been submitted and it will be reviewed and posted. The django version sends you directly to your new disclosure, which could allow you to post a link to it before it is reviewed and posted. (Should the view detail say "this is under review" instead of showing the disclousre?)

Yes. Bug in django version.

• The cgi version sends email to the secretariat (in the same general format as the preview) as a notification of the new submission.

Right. Bug (missing functionality) in django version.

If nothing else, the django version should at least send the same kind of email to keep the workflow the same.

Yes.

[ietf-svn-bot]

@michael.lee@neustar.biz commented

---

I have following differences:

• The cgi version allows you to submit an IPR without specifying Disclosure of Patent Information when you select 'Yes' on V.B. The django version doesn't do this.

• You can submit an ipr with mixed type of IETF documentations and other contribution (section IV). There was a discussion about this a while ago and this action was prohibited. We may want to bring this up to people like Russ or Scott Bradner if we want to change this rule. If changed, then we will need to test this with secreatariat's interface to make sure the notification messages are going out to proper group of people.

• There is no Review and Confirm page in django. May be this is intended?

Michael.

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

Replying to ietf-svn-conversion/datatracker#3 (comment:5):

I have following differences:

• The cgi version allows you to submit an IPR without specifying Disclosure of Patent Information when you select 'Yes' on V.B. The django version doesn't do this.

I think this should be fixed.

• You can submit an ipr with mixed type of IETF documentations and other contribution (section IV). There was a discussion about this a while ago and this action was prohibited. We may want to bring this up to people like Russ or Scott Bradner if we want to change this rule. If changed, then we will need to test this with secreatariat's interface to make sure the notification messages are going out to proper group of people.

I had a discussion with past chairs and others about permitting both RFCs and
drafts in the same disclosure (after having asked you (Michael) about this),
and got go-ahead on that.

Is this something different, or the same issue?

• There is no Review and Confirm page in django. May be this is intended?

No, but possibly sufficiently minor that we will fix it later.

Michael.

[ietf-svn-bot]

@fenner@research.att.com commented

---

Replying to ietf-svn-conversion/datatracker#3 (comment:5):

• You can submit an ipr with mixed type of IETF documentations and other contribution (section IV). There was a discussion about this a while ago and this action was prohibited. We may want to bring this up to people like Russ or Scott Bradner if we want to change this rule. If changed, then we will need to test this with secreatariat's interface to make sure the notification messages are going out to proper group of people.

I checked ipr_admin_detail.cgi, command=do_post_it - it uses both ipr_ids and ipr_rfcs and looks up the relevant people for each I-D and RFC individually and adds them all together, so it looks like it already supports it.

[ietf-svn-bot]

@henrik@levkowetz.com changed status from reopened to closed

[ietf-svn-bot]

@henrik@levkowetz.com changed resolution from `` to fixed

[ietf-svn-bot]

@henrik@levkowetz.com changed component from `` to admin/